cdf525897bffc445c4c860225ecb42eda5925a86: Bug 1507180 - Make copy of list before iterating over it r=dom-workers-and-storage-reviewers,sg
Yaron Tausky <ytausky@mozilla.com> - Wed, 04 Dec 2019 10:47:30 +0000 - rev 506470
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1507180 - Make copy of list before iterating over it r=dom-workers-and-storage-reviewers,sg Differential Revision: https://phabricator.services.mozilla.com/D55286
99abe5757ee597f98475e89bb1bd730708ecc67f: Bug 1592934 - Revert the accidental changes on D55653; r=janv
Tom Tung <ttung@mozilla.com> - Wed, 11 Dec 2019 10:40:49 +0000 - rev 506469
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1592934 - Revert the accidental changes on D55653; r=janv Differential Revision: https://phabricator.services.mozilla.com/D56711
c8b835687333e3534a7b8b942fdc240406320128: Bug 1602822 - [wpt-sync] Update web-platform-tests to 327fd564511f56819f0e9994bf450e648c7483a1, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 10 Dec 2019 17:00:26 +0000 - rev 506468
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1602822 - [wpt-sync] Update web-platform-tests to 327fd564511f56819f0e9994bf450e648c7483a1, a=testonly MANUAL PUSH: wpt sync bot wpt-head: 327fd564511f56819f0e9994bf450e648c7483a1 wpt-type: landing
29d8ceb3287202963c6ccf6f15cc5c52f406452a: Bug 1602606 [wpt PR 20689] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 10 Dec 2019 13:02:09 +0000 - rev 506467
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1602606 [wpt PR 20689] - Update wpt metadata, a=testonly wpt-pr: 20689 wpt-type: metadata
89d3cfc1e36c1b871e7fc7c500235b4cbea72401: Bug 1602606 [wpt PR 20689] - PerformAction API supports two pointer up actions in different ticks, a=testonly
Lan Wei <lanwei@chromium.org> - Tue, 10 Dec 2019 17:00:04 +0000 - rev 506466
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1602606 [wpt PR 20689] - PerformAction API supports two pointer up actions in different ticks, a=testonly Automatic update from web-platform-tests PerformAction API supports two pointer up actions in different ticks In ChromeDriver PerformAction API, we used to release all the touch points all once, because Devtool Input.dispatchTouchEvent API's touchEnd event will release all the touch points. https://chromedevtools.github.io/devtools-protocol/tot/ Input#method-dispatchTouchEvent In order to just release one touch point, we have to send touchMove event excluding the touch point we want to release from touch points list, so Devtool Input.dispatchTouchEvent will send a pointerup event for this touch point. Bug: 1020674 Change-Id: Iba44ef480284b44f914378374bc14d63cf66a5c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1958163 Reviewed-by: John Chen <johnchen@chromium.org> Commit-Queue: Lan Wei <lanwei@chromium.org> Cr-Commit-Position: refs/heads/master@{#723137} -- First pass at adding expectations -- wpt-commits: 9e9a0defdf44857881fbdf35761bd1f1d5e7f50a, f0e2d156746a039e26db6805bd74f261d2730633 wpt-pr: 20689
fe75f68b4cabacec6fa8dc607994ba1cf3a24725: Bug 1602725 [wpt PR 20696] - Mark css-typed-om/idlharness.html as slow., a=testonly
Rune Lillesveen <futhark@chromium.org> - Tue, 10 Dec 2019 16:59:59 +0000 - rev 506465
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1602725 [wpt PR 20696] - Mark css-typed-om/idlharness.html as slow., a=testonly Automatic update from web-platform-tests Mark css-typed-om/idlharness.html as slow. Flakily timing out on multiple platforms. Bug: 1032318 Change-Id: Iff758bd9bc37f99355482004ccfe5b3b04bb6e07 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1960147 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#723311} -- wpt-commits: a13d8e5a42500c6b193369234c813a8dc34a0c5d wpt-pr: 20696
ff879187b45212f71fd275f92ccd7321d6817b73: Bug 1602427 [wpt PR 20679] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 10 Dec 2019 10:54:09 +0000 - rev 506464
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1602427 [wpt PR 20679] - Update wpt metadata, a=testonly wpt-pr: 20679 wpt-type: metadata
1e03af3235b6f5bb587f952443bf1e037aa89456: Bug 1602427 [wpt PR 20679] - [css-pseudo] Fix WPT test mismatch expectations for ::marker, a=testonly
Oriol Brufau <obrufau@igalia.com> - Tue, 10 Dec 2019 16:59:51 +0000 - rev 506463
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1602427 [wpt PR 20679] - [css-pseudo] Fix WPT test mismatch expectations for ::marker, a=testonly Automatic update from web-platform-tests [css-pseudo] Fix WPT test mismatch expectations for ::marker In some tests I added both "match" and "mismatch" conditions, expecting both of them to hold since that's how Chromium treats that. However, according to the docs, if a test has multiple conditions, they should be treated as an OR operator. This makes a test pass in Firefox even if the rendering is wrong. The proper way to check multiple conditions with the AND operator is adding the extra ones in the references. Spec: https://web-platform-tests.org/writing-tests/reftests.html#complex-pass-conditions Change-Id: Idb737e2486f2155f05a09a2c88bc1094c1b603e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1958128 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Oriol Brufau <obrufau@igalia.com> Cr-Commit-Position: refs/heads/master@{#723296} -- wpt-commits: bf028a7fa1d2edd9c4e6aa780d3844554eefbde1 wpt-pr: 20679
c31a843565acdba3f66dc17e19cd3228fa586b1c: Bug 1601999 [wpt PR 20659] - Inserting empty DocumentFragment results in no notifications, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Tue, 10 Dec 2019 16:59:46 +0000 - rev 506462
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1601999 [wpt PR 20659] - Inserting empty DocumentFragment results in no notifications, a=testonly Automatic update from web-platform-tests DOM: inserting empty DocumentFragment results in no notifications See https://github.com/whatwg/dom/pull/806. -- wpt-commits: 96a76ecb4cc72e0f269965973e2208b4ae7e4c01 wpt-pr: 20659
31831824a05c8c9f895af4959cf400e97026fcf9: Bug 1601639 [wpt PR 20634] - LazyLoad: Merge scroll.html into image-loading-lazy.tentative.html, a=testonly
Rob Buis <rbuis@igalia.com> - Tue, 10 Dec 2019 16:59:41 +0000 - rev 506461
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1601639 [wpt PR 20634] - LazyLoad: Merge scroll.html into image-loading-lazy.tentative.html, a=testonly Automatic update from web-platform-tests LazyLoad: Merge scroll.html into image-loading-lazy.tentative.html The two tests do the same thing but scroll.html checks for placeholder, so move that functionality into image-loading-lazy.tentative.html and remove scroll.html. Bug: 1031157 Change-Id: Id0b15fb1a2866933ecaa072a10f4fbc8655d033c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1952868 Commit-Queue: Rob Buis <rbuis@igalia.com> Reviewed-by: Dominic Farolino <dom@chromium.org> Cr-Commit-Position: refs/heads/master@{#723286} -- wpt-commits: 47ce520c84042b38642dae9cf9375a9c6411af26 wpt-pr: 20634
1e40e1d1e544f3910ad23b1dbe3953fb6e537462: Bug 1599685 [wpt PR 20472] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 10 Dec 2019 07:44:43 +0000 - rev 506460
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1599685 [wpt PR 20472] - Update wpt metadata, a=testonly wpt-pr: 20472 wpt-type: metadata
aaf1990089423f230eff5bfb4fb2bad3b9f60ba8: Bug 1599685 [wpt PR 20472] - [webnfc] Remove NDEFMessage{Init}#url and old impl of the author record., a=testonly
Leon Han <leon.han@intel.com> - Tue, 10 Dec 2019 16:59:33 +0000 - rev 506459
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1599685 [wpt PR 20472] - [webnfc] Remove NDEFMessage{Init}#url and old impl of the author record., a=testonly Automatic update from web-platform-tests [webnfc] Remove NDEFMessage{Init}#url and old impl of the author record. The plan is: 1. Introduces NDEFRecord{Init}#id and supports reading. Already done by crrev.com/c/1861574. 2. Supports writing. crrev.com/c/1928891 is focused on impl in Blink, with the following CLs focused on impl in Device Service. crrev.com/c/1910906 crrev.com/c/1911385 crrev.com/c/1915940 crrev.com/c/1916261 3. Introduces NFCScanOptions#id and filters records by it when scanning. Done by crrev.com/c/1936187. 4. Removes NDEFMessage{Init}#url and old impl of the author record. This CL. The spec changes: https://github.com/w3c/web-nfc/pull/338 https://github.com/w3c/web-nfc/pull/340 https://github.com/w3c/web-nfc/pull/446 BUG=520391 Change-Id: Id1c29d980426a5559fd6e30aa0fc95b268d8e96c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1938835 Commit-Queue: Leon Han <leon.han@intel.com> Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Fran├žois Beaufort <beaufort.francois@gmail.com> Cr-Commit-Position: refs/heads/master@{#723252} -- wpt-commits: fa41b43ac93bc2fdc2427a4378dc3754d483cdda wpt-pr: 20472
7ac8e218433a198a435db7ae46b8b5ba1faba834: Bug 1598469 [wpt PR 20375] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 10 Dec 2019 02:48:54 +0000 - rev 506458
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1598469 [wpt PR 20375] - Update wpt metadata, a=testonly wpt-pr: 20375 wpt-type: metadata
085f6082a04795398ea6e444f3bf48caecc8bdf5: Bug 1598469 [wpt PR 20375] - Allow another touch start happen when there are active touch points, a=testonly
Lan Wei <lanwei@chromium.org> - Tue, 10 Dec 2019 16:59:25 +0000 - rev 506457
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1598469 [wpt PR 20375] - Allow another touch start happen when there are active touch points, a=testonly Automatic update from web-platform-tests Allow another touch start happen when there are active touch points Now when there are active touch points and we dispatch a touch start, an error "Must have no prior active touch points to start a new touch." will throw out. We should allow this case happens: Input.dispatchEvent({ type: 'touchStart', touchPoints: [{ x: 100, y: 100, id: 1 }] }); Input.dispatchEvent({ type: 'touchStart', touchPoints: [{ x: 100, y: 100, id: 1 }, { x: 150, y: 100, id: 2 }] }); Bug: 1020674 Change-Id: Ib5cae40864312977f03b2c9671edd7c46637be7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1927951 Commit-Queue: Lan Wei <lanwei@chromium.org> Reviewed-by: Andrey Kosyakov <caseq@chromium.org> Cr-Commit-Position: refs/heads/master@{#718846} -- Add failure expectations for the new test -- Move expectations to subtest -- Update expectations -- ERROR not FAIL for Firefox -- Take 3 at getting expectations right -- Safari ERROR, Chrome pass -- wpt-commits: a8713f43245a55c7577ba7941155dc527e574741, d5fd6a2b710ca73b8c2c8eec4d17512eae666f0a, 0482f27a7ec26435879c0cf34c71397625162134, 0fa6b74d3ad61d3ea3334d2331ec87ca55676393, 201003ca81203163e22c74d7f8160653aee3fa50, cb5fc41f4db7b40e94c46ccbdfc9c27d5dcf8fd8, 9a4b9e1b39bb6269430b1658a814b371c5f3bf32 wpt-pr: 20375
52ddf9e95cc3a1c79aa49a6666d3d5109eb47737: Bug 1602822 [wpt PR 20641] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 09 Dec 2019 20:51:15 +0000 - rev 506456
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1602822 [wpt PR 20641] - Update wpt metadata, a=testonly wpt-pr: 20641 wpt-type: metadata
216fe978db6d0adaf9b1b66fdfbb148c6dc3c59e: Bug 1602822 [wpt PR 20641] - Fugu: Move getScreens() onto the Window interface, a=testonly
Mike Wasserman <msw@chromium.org> - Tue, 10 Dec 2019 16:59:17 +0000 - rev 506455
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1602822 [wpt PR 20641] - Fugu: Move getScreens() onto the Window interface, a=testonly Automatic update from web-platform-tests Fugu: Move getScreens() onto the Window interface Update code to better match the latest Screen Enumeration proposal: https://github.com/spark008/screen-enumeration/blob/master/EXPLAINER.md Move getScreens() off a constructable IDL class and Navigator interface. See discussion in https://github.com/spark008/screen-enumeration/issues/9 Only expose getScreens() to Window-accessible execution contexts for now. We can support Worker execution contexts later, as use cases arise. (mfoltz@ recommended this limited/incremental approach) Test with chrome://flags#enable-experimental-web-platform-features or --enable-blink-features=ScreenEnumeration Bug: 994889 Test: Automated; window.getScreens() works as expected with the flag. Change-Id: I955e21bd0691d36ddb9d8f667d86863004e20091 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1952023 Commit-Queue: Michael Wasserman <msw@chromium.org> Reviewed-by: Domenic Denicola <domenic@chromium.org> Reviewed-by: Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#723061} -- wpt-commits: 928d8accdea0d2e11ae93ff2c0544ed6f2e0ce65 wpt-pr: 20641
3143076e02686d3f9f88c36ea001be059236bc0a: Bug 1602136 [wpt PR 20666] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 10 Dec 2019 01:14:08 +0000 - rev 506454
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1602136 [wpt PR 20666] - Update wpt metadata, a=testonly wpt-pr: 20666 wpt-type: metadata
5fd86c2a367b6de03c8b159d834640abc899798a: Bug 1602136 [wpt PR 20666] - SMS Receiver: Test for detached iframe, a=testonly
Ayu Ishii <ayui@chromium.org> - Tue, 10 Dec 2019 16:59:09 +0000 - rev 506453
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1602136 [wpt PR 20666] - SMS Receiver: Test for detached iframe, a=testonly Automatic update from web-platform-tests SMS Receiver: Test for detached iframe Bug: 1027394 Change-Id: Ife6c3b001253d5fec64c3b6e9d4b5b9d6a7ba2e8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1956076 Commit-Queue: Ayu Ishii <ayui@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#723040} -- wpt-commits: cfa7532fc63d30acb16f9eb82ef30e718c2661d9 wpt-pr: 20666
a75eb297546190b81743b4452c12a79e7e87aa53: Bug 1588802 [wpt PR 19701] - Implement `Sec-CH-UA-Mobile`, a=testonly
Aaron Tagliaboschi <aarontag@chromium.org> - Tue, 10 Dec 2019 16:59:04 +0000 - rev 506452
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1588802 [wpt PR 19701] - Implement `Sec-CH-UA-Mobile`, a=testonly Automatic update from web-platform-tests Implement `Sec-CH-UA-Mobile` Mobile is a boolean client hint that informs whether a "mobile" or "desktop" user experience should be supplied. Relevant changes to the spec can be found here: https://github.com/WICG/ua-client-hints/pull/8 That was manually added via this commit: https://github.com/WICG/ua-client-hints/commit/db6fab2569b78666c40e84e4d0458dbdf59d336b Bug: 928669 Change-Id: Ia983cfa516c28b6a747b270abcc44e71ed39e1b5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1829793 Commit-Queue: Aaron Tagliaboschi <aarontag@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Reviewed-by: Dominick Ng <dominickn@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#723037} -- wpt-commits: 98e81ec707999187b087b3671e93a3625188b35a wpt-pr: 19701
55acee2cb32bef02a8b5b10bc95b364f85e82911: Bug 1599796 [wpt PR 20430] - [Trusted Types] Implement new <script> handling for Trusted Types., a=testonly
Daniel Vogelheim <vogelheim@chromium.org> - Tue, 10 Dec 2019 16:58:59 +0000 - rev 506451
Push 36904 by ncsoregi@mozilla.com at Wed, 11 Dec 2019 17:42:45 +0000
Bug 1599796 [wpt PR 20430] - [Trusted Types] Implement new <script> handling for Trusted Types., a=testonly Automatic update from web-platform-tests [Trusted Types] Implement new <script> handling for Trusted Types. This follows the proposal at https://github.com/w3c/webappsec-trusted-types/pull/236 and effectively reverts crrev.com/c/1547746. This replaces the (arguably rather invasive) changes in node.cc and element.cc with more elaborate logic in html_script_element.cc. (I.e., it pushes complexity from the super-classes into a specific subclass, at the expense of making the sub-class do more work.) Bug: 1026549 Change-Id: I929e9e669db7f9e6b8de5a3d0d0df661f109b644 -- wpt-commits: d1e31101085c0ce2563ec39c0315ef84d8d2562a wpt-pr: 20430
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip