9da50490d56aabaa7d4e7296e7fd1a8cbe759307: Bug 1454335 [wpt PR 10485] - fix: ApplePay PMI is wrong, a=testonly
Marcos Cáceres <marcos@marcosc.com> - Sun, 22 Apr 2018 16:46:35 +0000 - rev 468893
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1454335 [wpt PR 10485] - fix: ApplePay PMI is wrong, a=testonly Automatic update from web-platform-testsfix: ApplePay PMI is wrong (#10485) -- wpt-commits: b4cdc8ff4bda43c826fe7911e6d8e035390b90fd wpt-pr: 10485
76370b20f843901da98cdad4b7c441ffc774636a: Bug 1453382 [wpt PR 10421] - Fetch: align about:blank handling with the standard, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Sun, 22 Apr 2018 16:45:19 +0000 - rev 468892
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1453382 [wpt PR 10421] - Fetch: align about:blank handling with the standard, a=testonly Automatic update from web-platform-testsFetch: align about:blank handling with the standard See https://github.com/whatwg/fetch/commit/72fc2e787be663f5bc39c88665dd3c356abbca0f. Closes https://github.com/whatwg/xhr/issues/194. -- wpt-commits: fa62ac066402b280c37623ee9ec45489939781fc wpt-pr: 10421
ca808b7aae84fbac92e7f932ef811849f9797d1b: Bug 1454386 [wpt PR 9987] - Ensure cloneNode() does not preserve the prototype, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Sun, 22 Apr 2018 16:44:02 +0000 - rev 468891
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1454386 [wpt PR 9987] - Ensure cloneNode() does not preserve the prototype, a=testonly Automatic update from web-platform-testsEnsure cloneNode() does not preserve the prototype Closes https://github.com/whatwg/dom/issues/565. -- wpt-commits: 691673d4de5105fab16f3b1a1d8523a5e9699fee wpt-pr: 9987
1423cb3efbc550c9178b142016a3424cc4baebaa: Bug 1453646 [wpt PR 10444] - Improve handling of harness-level errors in wptrunner, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sun, 22 Apr 2018 16:40:22 +0000 - rev 468890
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1453646 [wpt PR 10444] - Improve handling of harness-level errors in wptrunner, a=testonly Automatic update from web-platform-testsImprove handling of harness-level errors in wptrunner (#10444) Split the internal handling of errors during a test into two cases; INTERNAL-ERROR that is produced if there's an exception in the harness and ERROR that is for exceptions reported by the test. Both are still reported as ERROR to the user, but in the INTERNAL-ERROR case the runner is always restarted, just like EXTERNAL-TIMEOUT, since we assume that the internal state is compromised somehow. -- wpt-commits: 6736e3f46bc6a110e6e550711208e492f1630eba wpt-pr: 10444
95d18c554b1bd335c2d1b535f448ab7251ad551a: Bug 1454153 [wpt PR 10469] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sun, 15 Apr 2018 12:09:13 +0000 - rev 468889
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1454153 [wpt PR 10469] - Update wpt metadata, a=testonly wpt-pr: 10469 wpt-type: metadata
61921a905038832ee4715729831d7fad92bb6ca0: Bug 1454153 [wpt PR 10469] - CSS: Remove support for position values with 3 parts, a=testonly
Eric Willigers <ericwilligers@chromium.org> - Sun, 22 Apr 2018 15:21:14 +0000 - rev 468888
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1454153 [wpt PR 10469] - CSS: Remove support for position values with 3 parts, a=testonly Automatic update from web-platform-testsCSS: Remove support for position values with 3 parts Intent: https://groups.google.com/a/chromium.org/d/msg/blink-dev/oBKMVCOX1sY/BLsXXiukAgAJ BUG=804187 Change-Id: I94e79b2b426250c521d0ebae1492571fde078f31 Reviewed-on: https://chromium-review.googlesource.com/1013459 Reviewed-by: Emil A Eklund <eae@chromium.org> Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Cr-Commit-Position: refs/heads/master@{#550915} -- wpt-commits: ff4cf69b8f1d705039d71ceef94dee04e74b35c9 wpt-pr: 10469
b52bee578d05fd5dcdbdc4d5c2bcca03619088e5: Bug 1452726 [wpt PR 10383] - [css-values] Typo fixes, a=testonly
Fuqiao Xue <xfq@w3.org> - Sun, 22 Apr 2018 15:19:38 +0000 - rev 468887
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1452726 [wpt PR 10383] - [css-values] Typo fixes, a=testonly Automatic update from web-platform-tests[css-values] Typo fixes (#10383) -- wpt-commits: fd2badfbfcfea30d9b61a306e4e73286eb001ec9 wpt-pr: 10383
5094751f1b75852a1bf9f1eb530e895e58fa08a0: Bug 1454073 [wpt PR 10465] - Reland "Web Animations: Fix bugs in procedure to process a keyframes argument", a=testonly
Stephen McGruer <smcgruer@chromium.org> - Sun, 22 Apr 2018 15:18:21 +0000 - rev 468886
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1454073 [wpt PR 10465] - Reland "Web Animations: Fix bugs in procedure to process a keyframes argument", a=testonly Automatic update from web-platform-testsReland "Web Animations: Fix bugs in procedure to process a keyframes argument" This is a reland of 0ade0386aa4168b48234bc7f33d30a62140b95ea Original change's description: > Web Animations: Fix bugs in procedure to process a keyframes argument > > There were three minor bugs left in the implementation: > > - We threw on lists-in-custom-iterators instead of just ignoring them. > - We returned all properties on the keyframe rather than just those > defined on the keyframe itself (e.g. we would include prototype > properties, against spec). > - We didn't access the properties in ascending unicode order. > > Bug: 827573 > Change-Id: I213ae5b24e1f35d7f28d16625025122950a6ba88 > Reviewed-on: https://chromium-review.googlesource.com/989261 > Reviewed-by: Kentaro Hara <haraken@chromium.org> > Reviewed-by: Yuki Shiino <yukishiino@chromium.org> > Reviewed-by: Robert Flack <flackr@chromium.org> > Commit-Queue: Stephen McGruer <smcgruer@chromium.org> > Cr-Commit-Position: refs/heads/master@{#550641} Bug: 827573 Change-Id: I6c49fa6ca36db16ecddfb520e0964bd231565a0b Reviewed-on: https://chromium-review.googlesource.com/1012897 Reviewed-by: Jeremy Roman <jbroman@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#550895} -- wpt-commits: da5837af9586234669a556c65fab521130688225 wpt-pr: 10465
af7fc0ffb660a06c33d4240eeea4508ef2411be3: Bug 1454160 [wpt PR 10470] - Sync Mozilla tests as of 2018-04-14, a=testonly
L. David Baron <dbaron@dbaron.org> - Sun, 22 Apr 2018 15:17:03 +0000 - rev 468885
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1454160 [wpt PR 10470] - Sync Mozilla tests as of 2018-04-14, a=testonly Automatic update from web-platform-testsSync Mozilla tests as of https://hg.mozilla.org/mozilla-central/rev/37b8862d354e0014a72715462dd2102dd5b599cc . (#10470) -- wpt-commits: 6f621cab194f3c3fe4f1a260e2ccd9115ed29679 wpt-pr: 10470
c52b25482f97ad671966ca7890526afedef92484: Bug 1454077 [wpt PR 10422] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 13 Apr 2018 21:53:27 +0000 - rev 468884
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1454077 [wpt PR 10422] - Update wpt metadata, a=testonly wpt-pr: 10422 wpt-type: metadata
de7ca81cd124d691b43c30172901697d04a3cdfe: Bug 1454077 [wpt PR 10422] - [cssom] Add tests for some recent CSSWG resolutions., a=testonly
Emilio Cobos Álvarez <emilio@crisal.io> - Sun, 22 Apr 2018 15:15:32 +0000 - rev 468883
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1454077 [wpt PR 10422] - [cssom] Add tests for some recent CSSWG resolutions., a=testonly Automatic update from web-platform-testsMerge pull request #10422 from emilio/cssom-woes [cssom] Add tests for some recent CSSWG resolutions. -- wpt-commits: 0e0344a7c493cf47088b776cb55c75e5f1d015c8 wpt-pr: 10422
1679673e1d64e59a265d8a08f5c883d9c3a78eb5: Bug 1454091 [wpt PR 10467] - Reland 2: Use PostTask to schedule cross-process postMessage forwarding., a=testonly
Alex Moshchuk <alexmos@chromium.org> - Sun, 22 Apr 2018 15:14:15 +0000 - rev 468882
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1454091 [wpt PR 10467] - Reland 2: Use PostTask to schedule cross-process postMessage forwarding., a=testonly Automatic update from web-platform-testsReland 2: Use PostTask to schedule cross-process postMessage forwarding. Changes from first reland attempt at https://crrev.com/c/1011287: - fix an additional source of flakiness in ChromeOS login tests Changes from original attempt at https://crrev.com/c/999182: - fix flakiness in two additional ChromeOS login tests - fix CSP WPT tests to not depend on ordering between iframe's onload and postMessage - see https://crbug.com/832319. Previously, we sent the IPC to forward a cross-process postMessage immediately. This caused a behavioral difference from the same-process case where the postMessage is always scheduled. Namely, in a scenario like this: frame.postMessage(...); doSomethingThatSendsIPCsToFrame(frame); the IPCs from JS following the postMessage would've been ordered incorrectly, causing |frame| to see their side effects after the postMessage dispatch in the cross-process case, whereas they would be seen before the postMessage dispatch in the same-process case. One example of this is frame.focus(), and another is a frame element onload event (dispatched via FrameHostMsg_DispatchLoad) arriving after a postMessage dispatched from an inline script while the frame was still loading. To resolve these ordering concerns, this CL changes cross-process postMessage to do a PostTask on the sender side before sending the message to the browser process. This improves the current state of the world, but does not yet achieve a perfect match for the IPC ordering in the same-process case - see discussion on the bug. Bug: 828529 Tbr: dcheng@chromium.org Change-Id: If2cc6591db31471adff0d84ec0b689905e21cdf1 Reviewed-on: https://chromium-review.googlesource.com/999182 Reviewed-by: Xiyuan Xia <xiyuan@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Alex Moshchuk <alexmos@chromium.org> Cr-Original-Original-Commit-Position: refs/heads/master@{#550284} Reviewed-on: https://chromium-review.googlesource.com/1011287 Cr-Original-Commit-Position: refs/heads/master@{#550621} Reviewed-on: https://chromium-review.googlesource.com/1012472 Cr-Commit-Position: refs/heads/master@{#550769} -- wpt-commits: c53d084cc57749bc666e42aaceeb34daa42539c7 wpt-pr: 10467
fb03c240a2e225003cc30b0f054a51fe26eb129f: Bug 1454070 [wpt PR 10464] - Revert "Web Animations: Fix bugs in procedure to process a keyframes argument", a=testonly
Avi Drissman <avi@chromium.org> - Sun, 22 Apr 2018 15:12:42 +0000 - rev 468881
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1454070 [wpt PR 10464] - Revert "Web Animations: Fix bugs in procedure to process a keyframes argument", a=testonly Automatic update from web-platform-testsRevert "Web Animations: Fix bugs in procedure to process a keyframes argument" This reverts commit 0ade0386aa4168b48234bc7f33d30a62140b95ea. Reason for revert: Unexpected Failures: * bindings/sequence-type.html * custom-elements/spec/define-element.html * external/wpt/custom-elements/CustomElementRegistry.html on https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Mac10.11%20%28dbg%29/ https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Linux%20Trusty%20%28dbg%29/ Speculatively reverting this to see if it's the cause. Original change's description: > Web Animations: Fix bugs in procedure to process a keyframes argument > > There were three minor bugs left in the implementation: > > - We threw on lists-in-custom-iterators instead of just ignoring them. > - We returned all properties on the keyframe rather than just those > defined on the keyframe itself (e.g. we would include prototype > properties, against spec). > - We didn't access the properties in ascending unicode order. > > Bug: 827573 > Change-Id: I213ae5b24e1f35d7f28d16625025122950a6ba88 > Reviewed-on: https://chromium-review.googlesource.com/989261 > Reviewed-by: Kentaro Hara <haraken@chromium.org> > Reviewed-by: Yuki Shiino <yukishiino@chromium.org> > Reviewed-by: Robert Flack <flackr@chromium.org> > Commit-Queue: Stephen McGruer <smcgruer@chromium.org> > Cr-Commit-Position: refs/heads/master@{#550641} TBR=flackr@chromium.org,yukishiino@chromium.org,jbroman@chromium.org,haraken@chromium.org,smcgruer@chromium.org Change-Id: I5e8dc0c67599492bd6e90fca4a034e29e334ef88 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 827573 Reviewed-on: https://chromium-review.googlesource.com/1012857 Reviewed-by: Avi Drissman <avi@chromium.org> Commit-Queue: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#550721} -- wpt-commits: cb845c5ab5e3c718f6de85ec6ac285770b9b394f wpt-pr: 10464
bd099c6fb9cf627af469bbdfd74ff77da43a5bbc: Bug 1454380 [wpt PR 8508] - Test that requestMediaKeySystemAccess sets label, a=testonly
theodab <theodab@google.com> - Sun, 22 Apr 2018 15:11:15 +0000 - rev 468880
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1454380 [wpt PR 8508] - Test that requestMediaKeySystemAccess sets label, a=testonly Automatic update from web-platform-testsTest that requestMediaKeySystemAccess sets label (#8508) On Edge, navigator.requestMediaKeySystemAccess ignores the value passed along to the label configuration field. This test exposes that bug. See https://goo.gl/6SgCRb -- wpt-commits: e6cffaa6d307ec6ef08102aad9c7a4a1df5b7d53 wpt-pr: 8508
4bbea84414ab0ea6b8abfc02c682c9e6c02e647e: Bug 1453792 [wpt PR 10454] - Make PointerEvent fromElement/toElement return null., a=testonly
Mustaq Ahmed <mustaq@google.com> - Sun, 22 Apr 2018 15:09:57 +0000 - rev 468879
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1453792 [wpt PR 10454] - Make PointerEvent fromElement/toElement return null., a=testonly Automatic update from web-platform-testsMake PointerEvent fromElement/toElement return null. Also added web-platform-tests. Blink intent thread: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/G2s1Ol3qcgA Closes https://github.com/w3c/pointerevents/issues/167 Bug: 827271 Change-Id: I8429b9541f8cfc38223b3a34116b74c2aba92ee5 Reviewed-on: https://chromium-review.googlesource.com/986877 Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Mustaq Ahmed <mustaq@chromium.org> Cr-Commit-Position: refs/heads/master@{#550683} -- wpt-commits: 81bcc8db4c676828d4b33ccb90c94049ffd831cf wpt-pr: 10454
2e40cf6fa01c585aedfb5e71c9a0233126f8a159: Bug 1454039 [wpt PR 10463] - Revert "Reland: Use PostTask to schedule cross-process postMessage forwarding.", a=testonly
Ben Pastene <bpastene@chromium.org> - Sun, 22 Apr 2018 15:08:40 +0000 - rev 468878
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1454039 [wpt PR 10463] - Revert "Reland: Use PostTask to schedule cross-process postMessage forwarding.", a=testonly Automatic update from web-platform-testsRevert "Reland: Use PostTask to schedule cross-process postMessage forwarding." This reverts commit 7c3d1d13f940e88ef6706fd8b5c257a81d340ed9. Reason for revert: WebviewLoginTest.Basic is still flaky on linux-chromeos-rel https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-rel/6886 https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-rel/6887 Original change's description: > Reland: Use PostTask to schedule cross-process postMessage forwarding. > > Changes from original attempt at https://crrev.com/c/999182: > - fix flakiness in two additional ChromeOS login tests > - fix CSP WPT tests to not depend on ordering between iframe's onload > and postMessage - see https://crbug.com/832319. > > Previously, we sent the IPC to forward a cross-process postMessage > immediately. This caused a behavioral difference from the > same-process case where the postMessage is always scheduled. Namely, > in a scenario like this: > > frame.postMessage(...); > doSomethingThatSendsIPCsToFrame(frame); > > the IPCs from JS following the postMessage would've been ordered > incorrectly, causing |frame| to see their side effects after the > postMessage dispatch in the cross-process case, whereas they would be > seen before the postMessage dispatch in the same-process case. One > example of this is frame.focus(), and another is a frame element > onload event (dispatched via FrameHostMsg_DispatchLoad) arriving after > a postMessage dispatched from an inline script while the frame was > still loading. > > To resolve these ordering concerns, this CL changes cross-process > postMessage to do a PostTask on the sender side before sending the > message to the browser process. This improves the current state of > the world, but does not yet achieve a perfect match for the IPC > ordering in the same-process case - see discussion on the bug. > > Bug: 828529 > Change-Id: I62a627c501526d09900be4f5bd2c899acf4d1e07 > Reviewed-on: https://chromium-review.googlesource.com/999182 > Reviewed-by: Xiyuan Xia <xiyuan@chromium.org> > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Commit-Queue: Alex Moshchuk <alexmos@chromium.org> > Cr-Original-Commit-Position: refs/heads/master@{#550284} > Reviewed-on: https://chromium-review.googlesource.com/1011287 > Cr-Commit-Position: refs/heads/master@{#550621} TBR=xiyuan@chromium.org,dcheng@chromium.org,alexmos@chromium.org Change-Id: Ic0637a6038bed6e5334a26e1934bee81faad3b9e No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 828529 Reviewed-on: https://chromium-review.googlesource.com/1012138 Reviewed-by: Ben Pastene <bpastene@chromium.org> Commit-Queue: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#550649} -- wpt-commits: 6ad1b51de7dce0d45d08cc0f47a92a7b1fed69d2 wpt-pr: 10463
5a85849690304374b25e7d7b30d4dd77b0c8dc3c: Bug 1450522 [wpt PR 10263] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sun, 01 Apr 2018 03:04:06 +0000 - rev 468877
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1450522 [wpt PR 10263] - Update wpt metadata, a=testonly wpt-pr: 10263 wpt-type: metadata
8469c16d69c5ac2b1e050428bfb571d7e53753d7: Bug 1450522 [wpt PR 10263] - Update serialization of timing functions, a=testonly
Eric Willigers <ewilligers@users.noreply.github.com> - Sun, 22 Apr 2018 15:07:14 +0000 - rev 468876
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1450522 [wpt PR 10263] - Update serialization of timing functions, a=testonly Automatic update from web-platform-testsMerge pull request #10263 from csnardi/patch-10 Update serialization of timing functions -- wpt-commits: 7b20d124d59d8d0e3e5b2f9da594e7b4aa1bcb1e wpt-pr: 10263
60ed7d758b1b4f5afaa636416cf3b5568316ca5e: Bug 1452989 [wpt PR 10399] - Web Animations: Fix bugs in procedure to process a keyframes argument, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Sun, 22 Apr 2018 15:05:57 +0000 - rev 468875
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1452989 [wpt PR 10399] - Web Animations: Fix bugs in procedure to process a keyframes argument, a=testonly Automatic update from web-platform-testsWeb Animations: Fix bugs in procedure to process a keyframes argument There were three minor bugs left in the implementation: - We threw on lists-in-custom-iterators instead of just ignoring them. - We returned all properties on the keyframe rather than just those defined on the keyframe itself (e.g. we would include prototype properties, against spec). - We didn't access the properties in ascending unicode order. Bug: 827573 Change-Id: I213ae5b24e1f35d7f28d16625025122950a6ba88 Reviewed-on: https://chromium-review.googlesource.com/989261 Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Yuki Shiino <yukishiino@chromium.org> Reviewed-by: Robert Flack <flackr@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#550641} -- wpt-commits: 2707869d65f3a4d5a1f2ab1d44920b19695a7cde wpt-pr: 10399
b5a7874d1f31011fc3ffc401ad16a05f546edb8d: Bug 1455843 [wpt PR 10462] - Accept variation in serialization of 'background', a=testonly
Eric Willigers <ewilligers@users.noreply.github.com> - Sun, 22 Apr 2018 15:04:40 +0000 - rev 468874
Push 9165 by asasaki@mozilla.com at Thu, 26 Apr 2018 21:04:54 +0000
Bug 1455843 [wpt PR 10462] - Accept variation in serialization of 'background', a=testonly Automatic update from web-platform-testsMerge pull request #10462 from ewilligers/background-serialization-variety Accept variation in serialization of 'background' -- wpt-commits: 1e5a5fefe15c4fcc1a3267daf1d75598f736c82f wpt-pr: 10462
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip