88fa5bd17cde18067f9ef26b10636a333e119e51: Bug 1646108 [wpt PR 24168] - Fix handling of remote frames and URLs in performance.measureMemory, a=testonly
Ulan Degenbaev <ulan@chromium.org> - Mon, 22 Jun 2020 10:44:55 +0000 - rev 536853
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1646108 [wpt PR 24168] - Fix handling of remote frames and URLs in performance.measureMemory, a=testonly Automatic update from web-platform-tests Fix handling of remote frames and URLs in performance.measureMemory The existing implementation measures memory usage of the main JS agent and reports URLs of the JS realms in the agent. The algorithm for mapping a JS realm to its reported URL walks the frame tree upwards to find the top-most cross-origin frame. The algorithm incorrectly assumed that all frames the path are local frames since the realms are local. This does not hold in the ABA case, where the main origin A embeds an iframe from origin B that in turn embeds an iframe from origin A. In such a case, the main JS realm and the grandchild realm are in the same JS agent and their frames are local. However, the child frame B is a remote frame. This CL fixes the algorithm to work both with local and remote frames. The URL of a remote frame can no longer be fetched from its document. Instead, it is fetched from the src attribute of the owner iframe element. This aligns with the upcoming spec and fixes the leak of post-server-redirect URLs. The CL also removes LocalFrame::FirstUrlCrossOriginToParent that is no longer needed. Bug: 1093880,1084999 Change-Id: I7a57a17701448d0fe210a66c7bdb8c0229fa5149 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2246175 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#780319} -- wpt-commits: 6221819cb0d18cee78ea5d011a8170b20a4fb5df wpt-pr: 24168
406df6d65cc57594968a45a1fe5ec067979ae53f: Bug 1646929 [wpt PR 24248] - [FragmentItem] Skip already added children in CreateBoxFragment, a=testonly
Koji Ishii <kojii@chromium.org> - Mon, 22 Jun 2020 10:44:50 +0000 - rev 536852
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1646929 [wpt PR 24248] - [FragmentItem] Skip already added children in CreateBoxFragment, a=testonly Automatic update from web-platform-tests [FragmentItem] Skip already added children in CreateBoxFragment FragmentItem keeps all inline items in a flat list. When inline box fragments are nested, |CreateBoxFragment| handles the same item twice; once for its parent and another for its grand parent. This patch fixes this by skipping non-direct children. Bug: 1096957 Change-Id: If5acba0c5bd687d156cc4530fbe6123bca9840ab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2251643 Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#780231} -- wpt-commits: 7fa40bc15a3af48dd0b6dd6d8cd16b109ac5d61e wpt-pr: 24248
28cfa6865c05bc6e48070f45e4c1ce0d9f8c46c3: Bug 1646907 [wpt PR 24247] - SELECT element: Fix a regression on adding multiple selected OPTIONs to a single-selection SELECT, a=testonly
Kent Tamura <tkent@chromium.org> - Mon, 22 Jun 2020 10:44:45 +0000 - rev 536851
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1646907 [wpt PR 24247] - SELECT element: Fix a regression on adding multiple selected OPTIONs to a single-selection SELECT, a=testonly Automatic update from web-platform-tests SELECT element: Fix a regression on adding multiple selected OPTIONs to a single-selection SELECT This CL fixes a regression caused by crrev.com/745230. Bug details: Suppose that |select.innerHTML = '<option selected>Option1' + '<option selected>Option2'| runs. Before crrev.com/745230, 1. Option1 is appended to the SELECT. 2. HTMLOptionElement::InsertedInto() and |HTMLSelectElement:: OptionInserted()| are called for Option1. 3. SelectOption(Option1) is called. 4. DeselectItemsWithoutValidation(Option1) is called 5. Option2 is appended to the SELECT. 6. HTMLOptionElement::InsertedInto() and |HTMLSelectElement:: OptionInserted()| are called for Option2. 7. SelectOption(Option2) is called. 8. DeselectItemsWithoutValidation(Option2) is called. Option1's selected state is cleared. Since crrev.com/745230, 1. Option1 is appended to the SELECT. 2. Option2 is appended to the SELECT. 3. HTMLSelectElement::ChildrenChanged() and |HTMLSelectElement:: OptionInserted()| are called for Option1. 4. SelectOption(Option1) is called. 5. DeselectItemsWithoutValidation(Option1) is called. Option2's selected state is cleared. 6. HTMLSelectElement::ChildrenChanged() and |HTMLSelectElement:: OptionInserted()| are called for Option2. 7. SelectOption(Option2) is NOT called because Option2's selected state was cleared. Fix: DeselectItemsWithoutValidation() should not update 'selected' state of OPTIONs for which OptionInserted() is not called yet. This CL adds a boolean flag to HTMLOptionElement, it represents whether OptionInserted() is called or not, and DeselectItemsWithoutValidation() checks the flag before updating 'selected' state. Bug: 1095725 Change-Id: If19b28c3edb877549ca498b661647466d03e6d1d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253260 Commit-Queue: Kent Tamura <tkent@chromium.org> Auto-Submit: Kent Tamura <tkent@chromium.org> Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#780174} -- wpt-commits: e75a8342e588e36a6ab387846a50d077621143b4 wpt-pr: 24247
7bdb48de0eaee90fe970078b5c28f4fe413f7297: Bug 1646879 [wpt PR 24244] - [FileAPI] Properly set charset when loading blob URL., a=testonly
Marijn Kruisselbrink <mek@chromium.org> - Mon, 22 Jun 2020 10:44:38 +0000 - rev 536850
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1646879 [wpt PR 24244] - [FileAPI] Properly set charset when loading blob URL., a=testonly Automatic update from web-platform-tests [FileAPI] Properly set charset when loading blob URL. Bug: 1086845 Change-Id: I1630dcff89198ea968ff49ff353d793ae19c10b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253242 Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Reviewed-by: Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#780118} -- wpt-commits: 80a7c1baefc0eacfb045a0d6cb35befbc7b54c66 wpt-pr: 24244
f4c08ad7631b1da1a7315e05e371ee975c374ba1: Bug 1646239 [wpt PR 24177] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 19 Jun 2020 03:50:37 +0000 - rev 536849
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1646239 [wpt PR 24177] - Update wpt metadata, a=testonly wpt-pr: 24177 wpt-type: metadata
f468703d8535544aa322cf833519cb2f7eec8003: Bug 1646239 [wpt PR 24177] - Add getWindowSegments JavaScript API, a=testonly
Daniel Libby <dlibby@microsoft.com> - Mon, 22 Jun 2020 10:44:30 +0000 - rev 536848
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1646239 [wpt PR 24177] - Add getWindowSegments JavaScript API, a=testonly Automatic update from web-platform-tests Add getWindowSegments JavaScript API This change builds on crrev.com/c/2229668 to plumb the window segment information from the content layer into Blink, where it is exposed via a JavaScript API. From RenderWidget, the root window segments are stored on the local WebFrameWidgetBase root, and returned via script through the FrameWidget interface. i2p: https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/_1_ljYsaqrU/qOoHJ7MhAgAJ Explainer: https://github.com/webscreens/window-segments/blob/master/EXPLAINER.md Change-Id: I9b80f189e41160fc490bd09191722cb20b7115e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2246988 Commit-Queue: Daniel Libby <dlibby@microsoft.com> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#780102} -- wpt-commits: 565dbc0bd35f3c4d34ad8c3fac0593d64d85bae9 wpt-pr: 24177
eae3eced148f41177408b1949e9f7c4707f26271: Bug 1646422 [wpt PR 24198] - blink: make LayoutBlock::RemovePositionedObject remove other objects, a=testonly
Scott Violet <sky@chromium.org> - Mon, 22 Jun 2020 10:44:25 +0000 - rev 536847
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1646422 [wpt PR 24198] - blink: make LayoutBlock::RemovePositionedObject remove other objects, a=testonly Automatic update from web-platform-tests blink: make LayoutBlock::RemovePositionedObject remove other objects This changes RemovePositionedObjects to remove any fixed-pos descendants. This ensures that if the removed object is added back, it doesn't end up after any descendants, which would cause out of order layout. BUG=1092887 TEST=webkit-box-fixed-position-child.html Change-Id: I41f01bad74048cf4983f0dda5fe0f073b3eb38f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2248136 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#779840} -- wpt-commits: 5756870d039495439b8512c26db05f25aaa3a0d7 wpt-pr: 24198
fb8880027ccc3461bfc050029fc16353b47c5c6d: Bug 1646679 [wpt PR 24233] - Fix timeout on RTCRtpTransceiver test., a=testonly
Harald Alvestrand <hta@chromium.org> - Mon, 22 Jun 2020 10:44:16 +0000 - rev 536846
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1646679 [wpt PR 24233] - Fix timeout on RTCRtpTransceiver test., a=testonly Automatic update from web-platform-tests Fix timeout on RTCRtpTransceiver test. This CL should make the test run consistently and always finish; we break out early from the test that was failing rather than waiting forever. Bug: chromium:869126 Change-Id: Ic52fbf0dea69a03645165a073354f61a3d28ad81 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2250065 Commit-Queue: Harald Alvestrand <hta@chromium.org> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#779810} -- wpt-commits: e3b772cdc0498672231311012995a6a1c7d9fbff wpt-pr: 24233
d55974431473f1bb534fbd4d20dc4e3c8004c39b: Bug 1646147 [wpt PR 24171] - wpt: fix webrtc simulcast rids, a=testonly
Philipp Hancke <philipp.hancke@googlemail.com> - Mon, 22 Jun 2020 10:44:11 +0000 - rev 536845
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1646147 [wpt PR 24171] - wpt: fix webrtc simulcast rids, a=testonly Automatic update from web-platform-tests wpt: fix webrtc simulcast rids which need an extra parenthesis since this should be an object as shown in https://w3c.github.io/webrtc-pc/#rtcrtpencodingspatialsim-example* Noticed in https://github.com/fippo/simulcast-playground/pull/7 BUG=None Change-Id: I176a2919a3dbd3e6b065dca9dcef357a1e2adc01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2247035 Reviewed-by: Harald Alvestrand <hta@chromium.org> Commit-Queue: Harald Alvestrand <hta@chromium.org> Cr-Commit-Position: refs/heads/master@{#779785} -- wpt-commits: 52a9f1c847e094e7925ae69bcc5bf4ff40826e45 wpt-pr: 24171
66944f0e6639faca7de7b6df84da977b82abece0: Bug 1643477 [wpt PR 23998] - Check for first frame in CreateImageBitmap, a=testonly
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> - Mon, 22 Jun 2020 10:44:06 +0000 - rev 536844
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1643477 [wpt PR 23998] - Check for first frame in CreateImageBitmap, a=testonly Automatic update from web-platform-tests Check for first frame in CreateImageBitmap (#23998) HTMLVideoElement::CreateImageBitmap is currently rejecting valid calls, when we have an available first frame, but the ready state hasn't been updated. This CL updates CreateImageBitmap to check for a valid frame, which amounts to having a first frame available. This CL also updates some WPTs to use preload=auto, to allow video elements to load without being visible, and yield expected results when calling CreateImageBitmap. Bug: 1090960 Change-Id: I21302a9c3433bf8218a75c3f6918bc20f4d36ca3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2231453 Auto-Submit: Thomas Guilbert <tguilbert@chromium.org> Reviewed-by: Kenneth Russell <kbr@chromium.org> Commit-Queue: Thomas Guilbert <tguilbert@chromium.org> Cr-Commit-Position: refs/heads/master@{#775670} Co-authored-by: Thomas Guilbert <tguilbert@chromium.org> -- wpt-commits: 55999f0667e5ae85e3bd80e6a1d2c6ff8eb6d988 wpt-pr: 23998
5a3f0059da33e1dd983c6ff0b2ee27a82b31001b: Bug 1645056 [wpt PR 24107] - [scroll-animations] Implement support for @scroll-timeline in the parser, a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Mon, 22 Jun 2020 10:44:01 +0000 - rev 536843
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1645056 [wpt PR 24107] - [scroll-animations] Implement support for @scroll-timeline in the parser, a=testonly Automatic update from web-platform-tests [scroll-animations] Implement support for @scroll-timeline in the parser This CL adds: - Parser support for the @scroll-timeline rule itself. - Parser support for the associated descriptors. - A partial CSSOM API for the @scroll-timeline rule. It's currently not possible to add parser support for @scroll-timeline without also adding the CSSOM wrapper, hence this is done in the same CL. Parsing a @scroll-timeline rule emits a StyleRuleScrollTimeline object, whereas the CSSOM API is implemented via CSSScrollTimelineRule, which wraps the StyleRuleScrollTimeline object. Since this CL is big enough already, the following has been postponed to later CLs: - StyleEngine integration. (Adding StyleRuleScrollTimeline to RuleSet, cascading @scroll-timeline rules, etc). - CSSScrollTimelineRule::cssText() (full-rule serialization). Bug: 1074052 Change-Id: Id5a51b3c7c269b852cb2e6de5414db44c710a87a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2240852 Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by: Nate Chapin <japhet@chromium.org> Reviewed-by: Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#779751} -- wpt-commits: df497b03b0f6f525ddea6f07516938fbcdb10d0c wpt-pr: 24107
a0aa8a4840605fbc403ca6c97469e82faf977170: Bug 1646307 [wpt PR 24184] - Python3: port tests in eventsource, a=testonly
Ziran Sun <zsun@igalia.com> - Mon, 22 Jun 2020 10:43:56 +0000 - rev 536842
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1646307 [wpt PR 24184] - Python3: port tests in eventsource, a=testonly Automatic update from web-platform-tests Python3: port tests in eventsource -- Correct type of body -- Remove unused module call -- wpt-commits: 8ed59ad76d99061cefe6582f83f025bb0d932881, 1433b4ee9a30bad77397ef120b0c6cbc49ed1bd2, 4c57283bfb189d2a871420184a8f09c276225bd4 wpt-pr: 24184
8599abc6d8058dd072e9db65ca36957629f3f7da: Bug 1646655 [wpt PR 24231] - [FragmentItem] Fix hit-testing floats in legacy root, a=testonly
Koji Ishii <kojii@chromium.org> - Mon, 22 Jun 2020 10:43:51 +0000 - rev 536841
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1646655 [wpt PR 24231] - [FragmentItem] Fix hit-testing floats in legacy root, a=testonly Automatic update from web-platform-tests [FragmentItem] Fix hit-testing floats in legacy root This patch fixes hit-testing floating objects in a legacy root. With |NGPaintFragment|, floats are in children, and that regular traversal can cover this case. With |FragmentItem|, floats are either in |NGFragmentItems| if it has an inline formatting context, or in children otherwise. This difference requires additional branch to the legacy fallback when hit-testing floating objects. Bug: 1096259 Change-Id: I8565eb663781318233c21482270804cf254e0aec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2249249 Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#779715} -- wpt-commits: 14b3e9ca5a0550410b17da2c07df74151c8ceced wpt-pr: 24231
eb0faf32f7577ceb4ddd1f5dfa21d69c3db3ee59: Bug 1646622 [wpt PR 24225] - Update requests to 2.24.0, a=testonly
pyup-bot <github-bot@pyup.io> - Mon, 22 Jun 2020 10:43:45 +0000 - rev 536840
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1646622 [wpt PR 24225] - Update requests to 2.24.0, a=testonly Automatic update from web-platform-tests Update requests from 2.23.0 to 2.24.0 -- Update requests from 2.23.0 to 2.24.0 -- Update requests from 2.23.0 to 2.24.0 -- wpt-commits: f2cc4c894dd9a920d6024636f7ba5f508afb9862, 3f23f8200ab40a01a749c0c07e0ca68e9bcb11aa, 3c6bb4c15db38e23cdfc8bf2299874c77fd8fe57 wpt-pr: 24225
c0d1c939f8b509b337f5b13bb68dc57dd28d5d72: Bug 1645295 [wpt PR 24130] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 18 Jun 2020 11:12:24 +0000 - rev 536839
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1645295 [wpt PR 24130] - Update wpt metadata, a=testonly wpt-pr: 24130 wpt-type: metadata
ecd53890ab847f0437d9392a6247a17a938c328c: Bug 1645295 [wpt PR 24130] - Set PictureInPictureWindow in leavepictureinpicture event, a=testonly
Francois Beaufort <beaufort.francois@gmail.com> - Mon, 22 Jun 2020 10:43:37 +0000 - rev 536838
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1645295 [wpt PR 24130] - Set PictureInPictureWindow in leavepictureinpicture event, a=testonly Automatic update from web-platform-tests Set PictureInPictureWindow in leavepictureinpicture event This CL makes sure PictureInPictureWindow is accessible from the leavepictureinpicture event so that users don't have to keep a reference to the PictureInPictureWindow object they got from the enterpictureinpicture event. Spec change: https://github.com/w3c/picture-in-picture/pull/189 Intent to ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/gwaEnJjtfKw Change-Id: Ibb6972596cd6b766bc2ed35cc6e360b7907c594d Bug: 1096350 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2241537 Reviewed-by: Jochen Eisinger <jochen@chromium.org> Commit-Queue: Fran├žois Beaufort <beaufort.francois@gmail.com> Cr-Commit-Position: refs/heads/master@{#779711} -- wpt-commits: 1449b69c394008d51cb625bd1adbde782c01e8be wpt-pr: 24130
f50ab929ee2e42f0bacb211d02471c60d03344b8: Bug 1644653 [wpt PR 24078] - wpt: screen enumeration: test to verify screen id, a=testonly
Arnaud Mandy <arnaud.mandy@intel.com> - Mon, 22 Jun 2020 10:43:32 +0000 - rev 536837
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1644653 [wpt PR 24078] - wpt: screen enumeration: test to verify screen id, a=testonly Automatic update from web-platform-tests wpt: screen enumeration: test to verify screen id Test to verify screen id. adding 3 displays to display vector. getScreens() should return 3 screens with ids 0,1,2. removing middle display from display vector. getScreens() should return 2 screens with ids 0,1. removing last display from display vector. getScreens() should return 1 screen with id 0. Bug: 1075656 Change-Id: Ib671b760353766d21330b95833b983c9b5e4737f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2238112 Reviewed-by: Michael Wasserman <msw@chromium.org> Commit-Queue: Arnaud Mandy <arnaud.mandy@intel.com> Cr-Commit-Position: refs/heads/master@{#779689} -- wpt-commits: df2272857e29491bdb6c8ab77a8adec2f11757d2 wpt-pr: 24078
7446debba5ecc55de7e2110e1952fee0a6dfbbce: Bug 1646578 [wpt PR 24212] - Don't show scrolling contents layers that are also backface-invisible., a=testonly
Chris Harrelson <chrishtr@chromium.org> - Mon, 22 Jun 2020 10:43:27 +0000 - rev 536836
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1646578 [wpt PR 24212] - Don't show scrolling contents layers that are also backface-invisible., a=testonly Automatic update from web-platform-tests Don't show scrolling contents layers that are also backface-invisible. In this situation, we have an element like this: <div id=target style="transform: ...; backface-visibility: hidden; overflow: scroll"> </div> It will have two transform and one for scrolling: Transform ScrollTranslation However, overflow clipping is also a grouping property [1], so the ScrollTranslation will have flattens_inherited_transform true regardless of the transform-style style of #target. With TransformInterop on, definitely the scrolling contents should not be shown (except for pseudo- and stacking context descendants). This CL changes the behavior for non-TransformInterop also, because it doesn't seem reasonable to have the behavior the way it is right now. [1] https://drafts.csswg.org/css-transforms-2/#grouping-property-values Bug: 363609 Change-Id: Ib1f356e80644582120e37261d368f774cbcaa6e1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2246437 Auto-Submit: Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Philip Rogers <pdr@chromium.org> Reviewed-by: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#779637} -- wpt-commits: efb4718b09a0947c3b49dfe32aa2251a33df0aa9 wpt-pr: 24212
d81c68861c425e0533177eafce43a740813e9585: Bug 1646415 [wpt PR 24197] - Support for the prefers-reduced-data media query feature, a=testonly
Adam Argyle <argyle@chromium.org> - Mon, 22 Jun 2020 10:43:22 +0000 - rev 536835
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1646415 [wpt PR 24197] - Support for the prefers-reduced-data media query feature, a=testonly Automatic update from web-platform-tests Support for the prefers-reduced-data media query feature Intent to prototype: https://groups.google.com/a/chromium.org/d/msg/blink-dev/oNJTem41LBs/CA4Nx05aAwAJ Bug: 1051189 Change-Id: I2ff88a70858cf322725f50e40f979c9596f45b0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2083838 Commit-Queue: Adam Argyle <argyle@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#779564} -- wpt-commits: c799fc8610f0ef1baef40e2afd200ccc4d97eb9a wpt-pr: 24197
8043413835a77cbe4c203c1e42472bf25a5b4cfc: Bug 1646584 [wpt PR 24214] - Update interfaces/native-file-system.idl, a=testonly
autofoolip <auto@foolip.org> - Mon, 22 Jun 2020 10:43:17 +0000 - rev 536834
Push 37533 by dluca@mozilla.com at Tue, 23 Jun 2020 21:38:40 +0000
Bug 1646584 [wpt PR 24214] - Update interfaces/native-file-system.idl, a=testonly Automatic update from web-platform-tests Update interfaces/native-file-system.idl (#24214) Note: This file was recently manually updated in commit 553ab1a48e. This commit may revert some of those changes. Source: https://github.com/tidoust/reffy-reports/blob/10b9f36/ed/idl/native-file-system.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/699526314 -- wpt-commits: 3683fb7847a7c3565661f1a494301b2b4fca6204 wpt-pr: 24214
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip