https://github.com/web-platform-tests/wpt

sort by:
Revision Author Date Message Commit Date
dfd7c3f Replaceable properties should be considered readonly. 14 June 2018, 16:17:28 UTC
55c9a77 Update the server-timing IDL file (#9831) 14 June 2018, 16:07:34 UTC
41a040a Improve :focus-visible tests - Add explanatory text to each one - Make the manual test path accessible to color blind testers - Bring headers up to date - Create a consistent style for :focus-visible and :focus:not(:focus-visible) for easier understanding of test results Bug: 817199 Change-Id: I97191d5c8395576a42c923a025d05d2d61e79552 Reviewed-on: https://chromium-review.googlesource.com/1093697 Commit-Queue: Alice Boxhall <aboxhall@chromium.org> Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org> Cr-Commit-Position: refs/heads/master@{#567266} 14 June 2018, 15:31:12 UTC
a639bff Sync Mozilla tests as of https://hg.mozilla.org/mozilla-central/rev/91db0c695f0272f00bf92c81c471a85101056d96 . (#11505) 14 June 2018, 14:50:30 UTC
0872560 Clean up the webaudio idl test and add long timeout Bug: 851320 Change-Id: I562fe492be73b0ad8929d8ae8be158230103157f Reviewed-on: https://chromium-review.googlesource.com/1095640 Reviewed-by: Raymond Toy <rtoy@chromium.org> Commit-Queue: Luke Bj <lukebjerring@chromium.org> Cr-Commit-Position: refs/heads/master@{#567231} 14 June 2018, 13:01:02 UTC
55d4477 docs: Add missing "be" to testharness' documentation 14 June 2018, 12:53:45 UTC
73f8f23 Fail early if Feature Policy is not supported (#11270) Part of #11269. 14 June 2018, 12:43:34 UTC
cf68763 PaymentRequest "paymentmethodchanged" event (#10912) 14 June 2018, 12:16:32 UTC
f556cda [LayoutNG] Avoid creating empty lines at bogus (unset) BFC offset 0,0. This affects auto-positioned out-of-flow nodes that are handled as part of inline layout, and other things too. This fix will also make it possible to use the position of the last child fragment to calculate the block size of a block (which I happen to be working on). Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng;master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: Ie3f99d850de81bd349e89c624f86cce95b38eede Reviewed-on: https://chromium-review.googlesource.com/1098925 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#567170} 14 June 2018, 06:39:23 UTC
b12b605 [docs] Add instruction for specifying test title 14 June 2018, 04:40:49 UTC
1110f36 Update webusb test Upstream re-attempt at https://github.com/web-platform-tests/wpt/pull/9854. Adds more untested IDL deps. Change-Id: Icf7bda0f264ec66f4980e0742485eb406e334c19 Reviewed-on: https://chromium-review.googlesource.com/1089862 Commit-Queue: Luke Bj <lukebjerring@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#567118} 14 June 2018, 03:55:25 UTC
66f3830 Avoid ~infinite table max logical width inside flex and grid containers. An infinite (or actually kTableMaxWidth, which is 1000000px) max logical width doesn't work well inside flexboxes, because LayoutFlexibleBox::ComputeInnerFlexBaseSizeForChild() will use a child's MaxPreferredLogicalWidth() as main axis extent if it's auto. Grid containers have similar issues with such tables, so avoid it for them as well. Don't apply this to deprecated flexbox, as that would cause two tests failures: * fast/block/block-size-integer-overflow.html * fast/deprecated-flexbox/box-size-integer-overflow.html Bug: 850566 Change-Id: I9984459801ac229575e8177a9d683088e723db6c Reviewed-on: https://chromium-review.googlesource.com/1095220 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#567032} 13 June 2018, 23:18:56 UTC
3172a6c webdriver: add element_click tests (#11453) 13 June 2018, 23:01:26 UTC
c941a55 Fix WptreportFormatter support for mozlog suites with no run_info Per the mozlog docs run_info is "an optional dictionary" 13 June 2018, 17:40:33 UTC
4fd6e87 Fix #10026: add test execution time to wptreport.json format 13 June 2018, 17:40:33 UTC
fec5f26 fix `python wpt make-hosts-file` command in README for PowerShell on Windows 10 (#11367) 13 June 2018, 17:05:41 UTC
5a2bb75 Fix linter to not complain about META.yml (#11486) Fixes #11484. 13 June 2018, 15:34:02 UTC
a027205 Rename Feature Policy: document-stream-insertion It was proposed here https://github.com/WICG/feature-policy/pull/172 that "document-write" is a better name for this feature. This CL makes the naming change correspondingly. Bug: 841605 Change-Id: Id0a928fd3f6669eb3700736ff5770d4717d2b414 Reviewed-on: https://chromium-review.googlesource.com/1095328 Commit-Queue: Ehsan Karamad <ekaramad@chromium.org> Reviewed-by: Ian Clelland <iclelland@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Reviewed-by: Nasko Oskov <nasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#566829} 13 June 2018, 15:02:00 UTC
5f202c8 Test ascii-case-insensitivity of media query expressions bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1464091 gecko-commit: 32a24b5f542d6f14f11c8c2cc32180066c4c8b62 gecko-integration-branch: autoland gecko-reviewers: heycam 13 June 2018, 09:26:11 UTC
9bf1daa [idlharness.js] Support subsetTestByKey in idlharness (#11414) Fixes #11413. 13 June 2018, 09:13:34 UTC
4f741e6 Order both actual and expected in selftests (#11425) 12 June 2018, 22:42:42 UTC
c78f060 Auto-update the xhr IDL source (#11465) 12 June 2018, 21:53:08 UTC
2b9df3e Add css-paint-api IDL file with test (#9773) 12 June 2018, 21:51:53 UTC
e600ea2 Rename of OWNER files to META.yml 12 June 2018, 21:30:41 UTC
e4ef2f7 Merge pull request #11480 from gsnedders/c563-list-type-000-ref-fix Fix c563-list-type-000-ref to match the test 12 June 2018, 20:19:20 UTC
be5b31e Fix c563-list-type-000-ref to match the test 12 June 2018, 18:33:21 UTC
33280b7 Fix #11454: Set --verify-log-full to False for ci/check_stability.py (#11464) I'm not entirely sure why #10988 made this default to on, given that was a change of behaviour from before, so let's turn it back off given it's causing breakage, as documented in #11454. 12 June 2018, 18:13:57 UTC
98530fb Fix test flakiness around multi-threaded blob URL revocation. Registering a new blob URL in the worker will ensure (at least in chrome) that the revocation has been fully processed before the main thread tries to fetch the now revoked URL. Bug: 851942 Change-Id: I12e794682dbb5b34dc08fe2a7d398e3ba02aaffa Reviewed-on: https://chromium-review.googlesource.com/1097230 Reviewed-by: Joshua Bell <jsbell@chromium.org> Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/master@{#566460} 12 June 2018, 17:04:04 UTC
c81e348 Remove array destructuring for WebDriver execute async script tests IE does not support array destructuring in a `let` statement. This commit allows the execute_async_script tests for collections to run on IE 11. 12 June 2018, 16:16:11 UTC
692f3f4 Fix errors in external/wpt/RTCDTMFSender-insertDTMF.https.html. This is in preparation for RTCRtpTransceiver/Unified Plan support. Updated tests: insertDTMF() should throw InvalidStateError if transceiver.currentDirection is [recvonly/inactive] Just like the tests fixed in https://chromium-review.googlesource.com/c/chromium/src/+/1095275, the tests were not set up properly. Fixed the tests so that currentDirection is what it is supposed to be according to the test description. Also updated the tests to use async/await. These tests will pass when we support RTCRtpTransceiver (WIP CL: https://chromium-review.googlesource.com/c/chromium/src/+/1025771). Bug: 777617 Change-Id: I59eab4e4a15bb82e2dabe68d56f6d55b0e380e75 Reviewed-on: https://chromium-review.googlesource.com/1097083 Commit-Queue: Henrik Boström <hbos@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#566432} 12 June 2018, 16:01:56 UTC
a65ac19 Fix F401 (unused import) throughout tools/ (#11439) 12 June 2018, 15:41:50 UTC
73ed379 [css-grid] Content Alignment as part of the track sizing algorithm The CSS WG resolved [1] that Content Alignment should account to the track sizing algorithm. The sizing algorithm has been modified so that two new steps (1.5 and 2.5) were added to compute the Content Alignment offsets after resolving the columns' and rows' sizes respectively. This change decouples the Content Alignment logic from the tracks position, so that we can use it as part of the track sizing algorithm. I also had to store the whole ContentAlignmentData structure in two class attributes. We need both, position and distribution offsets, to be used in different parts of the layout logic. Finally, since the ContentAlignmentData is now used as persistent memory, we had to remove the STACK_ALLOCATED flag; hence, I think using DISALLOW_COPY_AND_ASSIGN and let the functions update the structure's internal field is a more efficient approach to commit this change. [1] https://github.com/w3c/csswg-drafts/issues/2557 Added WPT * grid-content-distribution-must-account-for-track-sizing-001.html * grid-content-distribution-must-account-for-track-sizing-002.html Bug: 844744 Change-Id: I90019a96b148d3713467e35fde9482d0d39b1ced Reviewed-on: https://chromium-review.googlesource.com/1067918 Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Reviewed-by: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#566412} 12 June 2018, 14:50:42 UTC
ce580da Clean up FileAPI idlharness tests After fixing #10338, we can leverage add_dependency_idls to import the 'real' untested idl from sources cleanly. 12 June 2018, 13:33:43 UTC
c08f464 nit wpt/webrtc/: Fix missing argument in RTCPeerConnection-getStats. TBR=guidou@chromium.org NOTRY=True Bug: 777617 Change-Id: Ia6e81728d3dfac35c9b1724252e7539b3aae181a Reviewed-on: https://chromium-review.googlesource.com/1096944 Reviewed-by: Henrik Boström <hbos@chromium.org> Commit-Queue: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#566381} 12 June 2018, 11:30:01 UTC
05c1a1f custom-elements: Element created by createElementNS(ns, qname, options) with valid custom element name and undefined options should be upgraded immediately createElementNS(XHTML_NS, 'my-element', undefined) was not being upgraded immediatedly, though both createElementNS(XHTML_NS, 'my-element') and createElementNS(XHTML_NS, 'my-element', {}) were. Bug: 841725 Change-Id: Iccc4f0e98b1de65288381dd9ac106e71bfc5d0c8 Reviewed-on: https://chromium-review.googlesource.com/1096812 Reviewed-by: Yoichi Osato <yoichio@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#566374} 12 June 2018, 10:36:03 UTC
ae0eec1 Fix errors external/wpt/RTCPeerConnection-removeTrack.https.html. This is in preparation for RTCRtpTransceiver/Unified Plan support. "Calling removeTrack with valid sender should set sender.track to null" Asserting that direction changes from 'sendrecv' to 'recvonly', this is explicit in the spec[1]. "Calling removeTrack with currentDirection blah should set direction to blah" The tests that meant to set up currentDirection to be 'sendrecv' or 'recvonly' before removeTrack() were incorrect. Tests updated to set up currentDirection correctly. Also updated them to use async/await because that's much nicer. These all fail because we don't have transceivers yet, but when running these changes in the RTCRtpTransceiver WIP CL[2], they all pass. [1] See step 10 of https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-removetrack [2] https://chromium-review.googlesource.com/c/chromium/src/+/1025771/ Bug: 777617 Change-Id: Ie3c077d14ea30038a06a98ecbeea475ac824dd9c Reviewed-on: https://chromium-review.googlesource.com/1095275 Reviewed-by: Guido Urdaneta <guidou@chromium.org> Commit-Queue: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#566366} 12 June 2018, 10:26:20 UTC
ed8650a Merge pull request #11335 from frivoal/git-doc-lint Mention the lint tool in the github tutorial 12 June 2018, 09:36:37 UTC
67ad035 Add web platform test for Accept-CH-Lifetime header for client hints Bug: 817049 Change-Id: Ic58e5688b0bb14803a9b6f01100500dd567b9fbc Reviewed-on: https://chromium-review.googlesource.com/1066919 Commit-Queue: Tarun Bansal <tbansal@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#566359} 12 June 2018, 09:01:35 UTC
2eeb9f0 Phrasing improvements and typo fixes 12 June 2018, 06:27:56 UTC
af6293e [css-contain] Size containment should ignore contents in flexbox/grid The spec is pretty clear (https://drafts.csswg.org/css-contain/#containment-size): "1. When laying out the containing element, it must be treated as having no contents." The patch modifies ComputeIntrinsicLogicalWidths() and FirstLineBoxBaseline() in LayoutFlexibleBox and LayoutGrid, so the contents are ignored if the flex or grid container has "contain: size". Buttons are implemented as flexboxes internally, so they get fixed too thanks to this change. BUG=850169 TEST=external/wpt/css/css-contain/contain-size-button-001.html TEST=external/wpt/css/css-contain/contain-size-flexbox-001.html TEST=external/wpt/css/css-contain/contain-size-grid-001.html Change-Id: Ia08c2c7b31126911cb4f0d1fc70aa444c22af8e3 Reviewed-on: https://chromium-review.googlesource.com/1093854 Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#566228} 12 June 2018, 02:01:26 UTC
be95940 Adjust test thresholds for win10 These tests fail on Windows 10 because the error thresholds are a bit too tight. Relax them a bit so that these pass on my Win10 machine. Bug: 851605 Change-Id: Ie7795205550a43928e7f0963e4411264e3ded37b Reviewed-on: https://chromium-review.googlesource.com/1095859 Reviewed-by: Hongchan Choi <hongchan@chromium.org> Commit-Queue: Raymond Toy <rtoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#566181} 11 June 2018, 23:08:40 UTC
0899588 [testharness.js] Extend test suite with "variants" Feature description (from modification to `README.md` file): > `testharness.js` is expected to function consistently in a number of > distinct environments. In order to verify this expectation, each functional > test may be executed under a number of distinct conditions. These conditions > are applied using WPT's "test variants" pattern. The available variants are > defined in the `variants.js` file; this file must be included before > `testharness.js`. Every test must specify at least one variant. Extend test harness for `testharness.js` with additional validation to ensure that each test is correctly formatted. Introduce a minimal UI to help future contributors discover this new functionality and its motivation. 11 June 2018, 21:04:28 UTC
46fe680 [sensors] Check that sensor frame and focused frame of same origin In order to implement mitigation stragegy defined in [1], focused frame and frame associated with the sensor should be of the same origin. [1] https://www.w3.org/TR/generic-sensor/#focused-area Bug: 849501 Change-Id: I06fce4e66873cd98e59e45d00ffe27de8e7d66f9 Reviewed-on: https://chromium-review.googlesource.com/1087049 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Commit-Queue: Alexander Shalamov <alexander.shalamov@intel.com> Cr-Commit-Position: refs/heads/master@{#566096} 11 June 2018, 19:59:32 UTC
8b2d92a Offscreen canvas: make worker tests catch errors Part of #11269. 11 June 2018, 19:05:44 UTC
32f74fe "Scroll an element into view" in HTML spec I use assert_approx_equals here since properties of DOMRect are of type double. For https://github.com/whatwg/html/pull/3131. 11 June 2018, 19:01:42 UTC
2c4b6f9 HTML: Run a history navigation test in a popup to report a result (#11296) Part of #11269. 11 June 2018, 16:15:46 UTC
acba5ff Update one final occurence of "w3c/web-platform-tests" (#11456) 11 June 2018, 15:14:53 UTC
8366faf Add two screen-orientation tests and replace async by promise_test 11 June 2018, 14:53:55 UTC
c517890 Sync Mozilla tests as of https://hg.mozilla.org/mozilla-central/rev/9941eb8c3b29d152851220b5d9791326c35e1c68 . (#11461) 11 June 2018, 14:25:05 UTC
6c78554 nit wpt/webrtc/: Use assert_array_equals, not assert_equals In RTCPeerConnection-setRemoteDescription-offer.html. Bug: 777617 Change-Id: I43b579b6ca0cbc0e950a379dc519fac95ac18f58 Reviewed-on: https://chromium-review.googlesource.com/1095189 Reviewed-by: Guido Urdaneta <guidou@chromium.org> Commit-Queue: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#565971} 11 June 2018, 13:55:18 UTC
1622a02 webrtc wpt: add cleanup to close peerconnections adds a pc.close() to all RTCPeerConnections in promise_test and async_test. This is codemod-powered by this: https://github.com/fippo/webrtc-codemods/blob/e844b2467cbb76a231c113366b2451cf248f53bc/wpt-rtcpeerconnection-no-helpers BUG=836871 Change-Id: Iee84ef938bf477a55612b6012c6de464c6aea55b Reviewed-on: https://chromium-review.googlesource.com/1049983 Commit-Queue: Henrik Boström <hbos@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#565591} 11 June 2018, 13:28:44 UTC
044cb1b HTML: Use a URL that is more likely to fail to parse in img test (#11304) Part of #1126. 11 June 2018, 11:46:37 UTC
3d14e69 Fire RTCPeerConnection.onsignalingstatechange in the correct order. With this change, onsignalingstatechange always fires before the setLocalDescription's promise resolves. Before this change, signaling state changes were surfaced with callbacks firing separately from the callback that setLocalDescription or setRemoteDescription had completed. As a result, the result of a SLD/SRD operation was surfaced in two PostTasks instead of one. This could lead to flaky behavior where JavaScript task execeution cycles may or may not execute between PostTasks which lead to undefined order. Also when the signalingstatechange was surfaced to the JS thread the firing of the event was delayed by a task execution cycle due to ScheduleDispatchEvent. - If both PostTasks were handled in the same cycle, the event firing would be scheduled and the promise resolved, such that the promise's then() is invoked just before the event fires (scheduled after promise). This is NOT in accordance with the spec. - If onsignalingstatechange's PostTask was handled in its own cycle, the event would be scheduled such that by the time the setLocalDescription's callback's PostTask occurs resolving the promise, the event would fire before the promise's then(). This IS in accordance with the spec. With this change, the onsignalingstatechange event is fired without delay, and it is processed in by the same observer that handles the SLD/SRD callback, so the order is always guaranteed to be the same. In addition, this CL removes the usage of WebRTCPeerConnectionHandlerClient::SignalingState and relies on the webrtc::PeerConnectionInterface::SignalingState enum directly. This is part of the Onion Souping work (crbug.com/787254). Bug: 848768, 787254 Change-Id: I7bc10439c44c6ff6beab0289975295ff2e051b9c Reviewed-on: https://chromium-review.googlesource.com/1085302 Commit-Queue: Henrik Boström <hbos@chromium.org> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#565291} 11 June 2018, 09:52:56 UTC
eb37a99 webrtc wpt: remove test_state_change_event removes test_state_change_event which initiates a "subtest" using a shared peerconnection resource. BUG=836871 Change-Id: I692bb5826c83d0d36d4169858ab2872d41c03b30 Reviewed-on: https://chromium-review.googlesource.com/1074696 Commit-Queue: Henrik Boström <hbos@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#562844} 11 June 2018, 09:52:56 UTC
7b2cd8b Clean up budget-api idl test (#11445) Follow up for #9763 now that #10338 is resolved and we have #10381 too. 11 June 2018, 08:59:20 UTC
a25abdf HTML: add more document.domain tests (#11402) For https://github.com/whatwg/html/pull/3742. 11 June 2018, 08:57:39 UTC
cdf41ff Update the IDL generated content headers to the content from reffy-reports (#11333) 11 June 2018, 08:52:21 UTC
ce22baf [LayoutNG] Orthogonal flows need available inline size for min/max calculation. Provide a suitable constraint space when calculating min/max inline sizes for an orthogonal flow root. ComputeMinMaxSize() in NGBlockNode typically ended up creating its zero-sized constraint space, which would typically result in large block sizes (since there'd e.g. only be space for one word per line). Set percentage resolution size too, instead of leaving it at 0x0. Percentages are often unresolvable (i.e. indefinite), in which case we should of course refrain from resolving them, rather than resolving the percentage against zero (which we used to do). Add a DCHECK that we're always provided with a constraint space when calculating min/max for orthogonal flows, as using the zero-size one will not produce the correct result. Bug: 848225 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: Ic0aac380b2b733d3a55b25396c89584e4468899d Reviewed-on: https://chromium-review.googlesource.com/1090845 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Aleks Totic <atotic@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#565446} 11 June 2018, 08:42:38 UTC
fb908f9 Improve RTCPeerConnection-setRemoteDescription-tracks.https.html tests. Using async functions and promise_tests instead of then()-chains and async_tests. This makes them more readable, easier to maintain and shorter. Replaced RTCPeerConnection-helper.js function performOffer() with exchangeOffer()/exchangeAnswer()/exchangeOfferAnswer(). Updated tests that were performing multiple offers to perform a full offer/answer exchange whenever there were future offers to be made. Previously it would perform half of an offer/answer cycle before starting the next offer/answer, which under Unified Plan could lead to some unexpected failures. TBR=guidou@chromium.org Bug: 777617 Change-Id: Ib0305d55af5aef7f49b5418d4ba44ded9c84d5c6 Reviewed-on: https://chromium-review.googlesource.com/1082434 Reviewed-by: Henrik Boström <hbos@chromium.org> Commit-Queue: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#565234} 11 June 2018, 08:32:06 UTC
2436290 Add selector tests * Test invalid pseudo-class starting with a valid one * Test selector in :not() surrounded by spaces * Test :nth-child used twice in selector 10 June 2018, 14:24:38 UTC
9d009fc Sync Mozilla tests as of https://hg.mozilla.org/mozilla-central/rev/874dedd55599e4b87fe37a497a968c079f1cca69 . (#11451) 09 June 2018, 23:53:20 UTC
639812b Sync Mozilla tests as of https://hg.mozilla.org/mozilla-central/rev/062e1553dc91da5b7c58dbaa0b5348b2be0f91f2 . (#11450) 09 June 2018, 18:16:04 UTC
418538e webdriver: update the webdriver WebIDL and fix test (#9851) 09 June 2018, 17:30:45 UTC
c243b3c [idlharness.js] Clean up media-capabilities idl test Follow up for #11255 which was unable to use add_dependency_idls because of #10338. 09 June 2018, 13:07:33 UTC
4ce3dab Call document.close, triggering onload and making the test not time out. This fixes both uses of object-association.js. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1419297 gecko-commit: 2762fef0119bcd3e78d36e78b0b75b5448d35c85 gecko-integration-branch: autoland gecko-reviewers: smaug 09 June 2018, 12:09:52 UTC
88e6a35 Clean up mediasession idl test 09 June 2018, 03:53:37 UTC
4565dc5 [KeyboardMap] Blink module now handles iFrames and multiple calls This CL adds the following: - KeyboardMap now requires the caller to be a top-level, secure browsing context - Multiple calls to getKeyboardLayout() will now be given the same promise instead of it being timing dependent (the initial promise might get overwritten with the old logic) - Sequential calls to getKeyboardLayout() still get their own promise - All promise rejections will return a DOM exception (similar to KeyboardLock) - I've cleaned up KeyboardLock a bit as well so it has similar logic/formatting to what I added to KeyboardMap - Added several tests to KeyboardMap and fixed some failing cases BUG=832811 Change-Id: I4a03f68c239cff42b8840e9513257384038f04b4 Reviewed-on: https://chromium-review.googlesource.com/1093474 Commit-Queue: Joe Downing <joedow@chromium.org> Reviewed-by: Gary Kacmarcik <garykac@chromium.org> Cr-Commit-Position: refs/heads/master@{#565833} 09 June 2018, 03:51:44 UTC
132d12d Partially update DOMPoint, DOMQuad, DOMRect, DOMMatrix. Some notes: this does not fully bring us to compliance to the current spec. Instead, these are the fixes that I needed to make in order to make css/geometry/interfaces.html pass with the DOMPoint changes in the previous patches. I don't fully understand why that patch caused the test to fail the way it did, but it ended up being easier to fix our code than understand why the harness was falling over. The DOMQuad::QuadBounds class was the source of some confusion for me. Now that DOMRectReadOnly is a concrete class with members, I wanted to avoid wasting them. However, the spec is unclear as to whether a DOMQuad's bound's should be live -- that is because DOMQuad exposes DOMPoint, we can set its points after retrieving a QuadBounds object. Our current code is live, setting the points changes the QuadBounds. Chromium's current behavior is to never update the QuadBounds object. I've left our behavior untouched in this patch (and waste 4 doubles per QuadBounds object), but I am intending to file a bug to understand what the intent of the spec is. I wonder if the author intended the points to be DOMPointReadOnly instead. If so, we could simplify the DOMRectReadOnly code and get rid of the virtual getters, which would be nice. I also wasn't thrilled to put the DOMMatrix setters on the DOMMatrixReadOnly class, but for brevity and simplicity of implementation, I've made them public. I briefly considered making the setters protected on the ReadOnly version of the class, but I'm not convinced that having to explicitly make them public on the derived class is worth the extra copies of the names. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1186265 gecko-commit: d5eeebfcad8c217ae51b9b665446cf01ca5f65aa gecko-integration-branch: central gecko-reviewers: bz 08 June 2018, 22:26:28 UTC
9b7f441 URL: correct non-special URL's origin Fixup for 0e084a927078d434bcc1952a2ab99fb541f2c25d. 08 June 2018, 20:32:59 UTC
99eb0f6 Created a test file to directly test the InputFile class in test_request.py, bypassing the server. Found and fixed a bug where passing a file larger than the buffer in InputFile caused the server to crash. Found and fixed a bug where seeking to a position before the current position and calling read() immediately after falsely tried to assert the positions of _buf_pos and _file_pos. Added tests for these bugs. (#11415) 08 June 2018, 20:22:00 UTC
05e7c7c part 2 - Fix buggy tests. Test 67.js was expecting us to only parse out one server-timing-metric, and ignore "junk" after. But, according to the spec, we are only to ignore junk up to the point where we see either (1) another metric, or (2) a server-timing-param. The header sent has a param (dur=123.4), and we were parsing that correctly. Test 68.js was similar, but this time there was another metric (comma- separated) in the header, which we correctly parsed. The test expected us to ignore it as "junk". bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1460590 gecko-commit: 51202d93e2e34100774d030b5dbe8e15cc8d6f16 gecko-integration-branch: central gecko-reviewers: jgraham 08 June 2018, 17:03:32 UTC
7bc2ca9 service worker: Add long timeout to registration-updateviacache.https.html. The test is slow because it does a lot of registrations and updates. Bug: 850842 Change-Id: I5782e4e426e571a604929da7369c8474ffda88e5 TBR: robertma Reviewed-on: https://chromium-review.googlesource.com/1092958 Reviewed-by: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Robert Ma <robertma@chromium.org> Commit-Queue: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#565641} 08 June 2018, 16:51:50 UTC
ede8a37 [css-logical-properties-1] Add test case margin{-block,-inline}{-start,-end} (#11431) Spec is here: https://drafts.csswg.org/css-logical-props-1/#logical-prop. [Committer note]: This was split out of a larger mostly obsolete PR, https://github.com/web-platform-tests/wpt/pull/5284 08 June 2018, 15:58:24 UTC
3bc4498 Add the InputDeviceCapabilities IDL file with test (#9755) 08 June 2018, 15:47:34 UTC
24d1bbe [idlharness.js] Test exposure set of partial interfaces (#11419) 08 June 2018, 15:32:30 UTC
7684fe3 Add ResizeObserver IDL file with test (#9756) 08 June 2018, 14:06:50 UTC
82a7c89 Add css-masking IDL file with test (#9905) 08 June 2018, 14:05:23 UTC
8cce357 Update the performance-timeline and user-timing IDL files (#9837) Adds new any.js tests and removes the old ones. 08 June 2018, 13:59:45 UTC
36bb4d7 CSS Typed OM: Proper types for custom props during iteration. Currently, you get CSSUnparsedValues when iterating entries on the .computedStyleMap(), even for properties which are registered with a type. However, if you do .computedStyleMap().get(...) with a registered property, you _do_ get the correct type. This is because ComputedStyleCSSValueMapping::Get properly looks up the typed values on the ComputedStyle, but ::GetVariables does not; instead it directly returns the CSSVariableData for everything, regardless of registrations. This patch changes the behavior of iteration to use the same code path as .get(). This ensures that we either create a CSSCustomProperty- Declaration on the fly for unregistered properties, or we re-use the existing (and typed) CSSValue for registered properties. Note: I initially wanted to do a nested iterator thing here, but dropped it because we would anyway need a temp HashSet to avoid potential duplicates from the StyleInheritedVariables-root. Note: One caller of GetVariables() just wants the size. It's possibly a little overkill to create entire HashMap just to count something, but I don't want to resolve that here in the same patch. R=futhark@chromium.org, haraken@chromium.org Bug: 850072 Change-Id: I64bfb3cc22a377cf956420a9e64d47ca3daac1e2 Reviewed-on: https://chromium-review.googlesource.com/1090848 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Anders Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#565605} 08 June 2018, 11:17:17 UTC
185e07d Exclude more labels in "Reviewed but still open PRs" (#11378) 08 June 2018, 08:56:33 UTC
837fc78 Use `variant` for window-open-noopener Fixes #11049. 08 June 2018, 08:20:58 UTC
0e084a9 URL: test ' in queries For https://github.com/whatwg/url/pull/395. 08 June 2018, 07:44:28 UTC
fb6713e Revert "WebKit export of https://bugs.webkit.org/show_bug.cgi?id=186127 (#11279)" (#11424) This reverts commit 57fea798e1e933e1d5291608d9d12da661185bcb. According to @birtles, Mozilla CI can have several tens of seconds between two frames while the test assumes only hundreds of milliseconds. So this is likely to be flacky. 08 June 2018, 07:43:45 UTC
ee048e6 [PageLifecycle] Add sendBeacon to the freeze WPT test navigator.sendBeacon should be allowed during the onfreeze callback, there was no changes in the code needed to enable it since it is implemented using fetch-keepalive, that is already allowed. This CL adds a test to make sure that this does not regress. Bugi: chromium:838684 Change-Id: I71b628ccce4dfbf1f2bd012c24866cd908f56d30 Reviewed-on: https://chromium-review.googlesource.com/1091638 Reviewed-by: Shubhie Panicker <panicker@chromium.org> Commit-Queue: Fadi Meawad <fmeawad@chromium.org> Cr-Commit-Position: refs/heads/master@{#565478} 08 June 2018, 01:21:53 UTC
d64b47d Fix race condition within wpt test policy-inherited-correctly-by-plznavigate.html part 2. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1466508 gecko-commit: fac57eb7e7aaaa0c5396d39dc67eae2451754b9f gecko-integration-branch: central gecko-reviewers: bz 07 June 2018, 20:26:03 UTC
71aca0a Convert word-wrap to an alias of overflow-wrap word-wrap was previously defined as its own property in CSSProperties.json5, but with the same behavior as overflow-wrap. However, this meant that word-wrap showed up alongside word-wrap in cssText. This patch converts word-wrap to be an alias of overflow-wrap, as this will prevent the issue of both properties showing up in cssText and matches the resolution in https://github.com/w3c/csswg-drafts/issues/866. Bug: 679068 Change-Id: I3d415eb1cde9a92dffa2a045ba5fa8b015eeb2d7 Reviewed-on: https://chromium-review.googlesource.com/1073677 Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Chris Nardi <cnardi@chromium.org> Cr-Commit-Position: refs/heads/master@{#565331} 07 June 2018, 18:31:00 UTC
97f9d19 Revert "Ensure that Config's set of ports is generated atomically. (#11299)" (#11418) This reverts commit 7018426026884a23def559fc0528fd1f338d4679. Fixes #11397; per @jdm "my PR didn't help at all" hence reverting doesn't reintroduce any flakiness. 07 June 2018, 18:17:52 UTC
0f651ff Merge pull request #11396 from frivoal/css-ui-2664 [css-ui-4] link cursor over SVG links 07 June 2018, 16:28:49 UTC
92d0134 Add css-fonts IDL file with test (#9904) 07 June 2018, 15:44:31 UTC
dd8e0ac Merge pull request #11412 from web-platform-tests/sync_320e4fd58a3bd93b844d9596e72027d5f3781f3d Merge pull request #11412 from sync_320e4fd58a3bd93b844d9596e72027d5f3781f3d 07 June 2018, 13:02:26 UTC
ce1a1d3 Merge pull request #11411 from web-platform-tests/sync_90693712e87eed75ff61cb67176cff92b514985c Merge pull request #11411 from sync_90693712e87eed75ff61cb67176cff92b514985c 07 June 2018, 13:02:13 UTC
8670bf3 Merge pull request #11410 from web-platform-tests/sync_54ad86342ade28ef425cfb50a2e502170e844198 Merge pull request #11410 from sync_54ad86342ade28ef425cfb50a2e502170e844198 07 June 2018, 13:01:56 UTC
1bb7f08 Merge pull request #11409 from web-platform-tests/sync_d0e05e0d4283f03892b688225b0134a1b6af84e2 Merge pull request #11409 from sync_d0e05e0d4283f03892b688225b0134a1b6af84e2 07 June 2018, 13:01:41 UTC
320e4fd Implement read methods on FileReaderSync Upstreamed from https://github.com/servo/servo/pull/19511 [ci skip] 07 June 2018, 13:01:33 UTC
54ad863 move to wpt Upstreamed from https://github.com/servo/servo/pull/20858 [ci skip] 07 June 2018, 13:01:33 UTC
9069371 improve spec compliance of window.close Upstreamed from https://github.com/servo/servo/pull/20865 [ci skip] 07 June 2018, 13:01:33 UTC
d0e05e0 prevent overwriting of salvageable state in later prompt/unload steps Upstreamed from https://github.com/servo/servo/pull/20837 [ci skip] 07 June 2018, 13:01:33 UTC
bc87c81 Correctly detect when a multicol descendant becomes or ceases to be a containing block. When a descendant of a multicol container becomes a containing block for out-of-flow positioned objects, or ceases to be one, out-of-flow positioned children may become or cease to be a part of the fragmentation context. We didn't detect this correctly. We only checked for transforms (in addition to position:relative). Make sure we check for filters too, now that those also establish containing blocks. Bug: 847328 Change-Id: I7ab47860bb8d9f8d9b0256b25e1123c34f73e8f4 Reviewed-on: https://chromium-review.googlesource.com/1089336 Reviewed-by: Emil A Eklund <eae@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#565210} 07 June 2018, 12:46:59 UTC
005c381 service worker: Add test for CSS cross-origin access. Tests for https://chromium-review.googlesource.com/c/chromium/src/+/1088335 Bug: 848786 Change-Id: I39d71d9aa2d1c0522c7a386405128297f62a0b24 Reviewed-on: https://chromium-review.googlesource.com/1088719 Commit-Queue: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/master@{#565208} 07 June 2018, 12:38:45 UTC
81303e1 HTML: update hashchange/popstate event tests For https://github.com/whatwg/html/pull/3737. 07 June 2018, 12:22:39 UTC
back to top