6c802fcef1e724c04fcd127aebaac553c890eba4: Bug 1652131 [wpt PR 24565] - Rename some manual dynamic import tests, a=testonly
Domenic Denicola <d@domenic.me> - Fri, 17 Jul 2020 11:15:07 +0000 - rev 541064
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1652131 [wpt PR 24565] - Rename some manual dynamic import tests, a=testonly Automatic update from web-platform-tests Rename some manual dynamic import tests This properly follows the filename pattern at https://web-platform-tests.org/writing-tests/manual.html to allow them to be identified as manual. -- wpt-commits: 859527a3513029d2d529cd42fb5c9f65afe42d58 wpt-pr: 24565
ed0c2959459a5bd52e704fc147360757dc79e247: Bug 1652031 [wpt PR 24559] - Add missing test path for manifest during WPT syncing., a=testonly
Josh Matthews <josh@joshmatthews.net> - Fri, 17 Jul 2020 11:15:02 +0000 - rev 541063
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1652031 [wpt PR 24559] - Add missing test path for manifest during WPT syncing., a=testonly Automatic update from web-platform-tests Add missing test path for manifest during WPT syncing. -- Merge loading and updating manifest states when syncing. -- wpt-commits: 1075231e6c12d2f971fb4321d57db42a62f02216, 04210fcb5e8e84d0c04797a225d94c3a0fac1935 wpt-pr: 24559
138a8f059dcd7879119b6464fa5f8ade0a915f22: Bug 1652012 [wpt PR 24557] - Fix tools/ unit tests, a=testonly
Robert Ma <robertma@chromium.org> - Fri, 17 Jul 2020 11:14:57 +0000 - rev 541062
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1652012 [wpt PR 24557] - Fix tools/ unit tests, a=testonly Automatic update from web-platform-tests Fix tools/ unit tests (#24557) * [lint] Fix a type annotation This was introduced in #24520 accidentally. * Skip quic in pytest and coverage quic/ contains Python 3-only code that leads to warnings when running `pytest --cov` in Python 2. * Mark a test as expected to fail on Windows+py3 See #24561 for details. * Drive-by: change docker-worker schema URL -- wpt-commits: 8cb1c14b2bac8725dad6dedfb2c8d4af9d1ffbc8 wpt-pr: 24557
f2d81c219006dad087c6b185fe6b21b9dac9ce44: Bug 1651830 [wpt PR 24541] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 10 Jul 2020 20:04:59 +0000 - rev 541061
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651830 [wpt PR 24541] - Update wpt metadata, a=testonly wpt-pr: 24541 wpt-type: metadata
17cb2fe2abe2e502bc5593e0f9e3265a53cac3be: Bug 1651830 [wpt PR 24541] - Add some basic Oscillator tests, a=testonly
Raymond Toy <rtoy@chromium.org> - Fri, 17 Jul 2020 11:14:49 +0000 - rev 541060
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651830 [wpt PR 24541] - Add some basic Oscillator tests, a=testonly Automatic update from web-platform-tests Add some basic Oscillator tests Test the output of the OscillatorNode for a sine wave at various frequencies (including a negative frequency) against the exact mathematical output. The low frequencies are intended to test Chrome's interpolation algorithm. Since we use sine waves or custom waves with a very few known coefficients (without normalization), we know what the exact output should be. Bug: 1013118 Change-Id: Ie68ef5a8e6979aab70d0a4d4c24ee31810599f56 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2290693 Reviewed-by: Hongchan Choi <hongchan@chromium.org> Commit-Queue: Raymond Toy <rtoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#787297} -- wpt-commits: 980dc0c7625921634185a5369c05506196102b53 wpt-pr: 24541
047384b455a0ee165039f854d80b796922b05e01: Bug 1646979 [wpt PR 24252] - [scroll-animations] Integrate @scroll-timeline with animations, a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Fri, 17 Jul 2020 11:14:44 +0000 - rev 541059
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1646979 [wpt PR 24252] - [scroll-animations] Integrate @scroll-timeline with animations, a=testonly Automatic update from web-platform-tests [scroll-animations] Integrate @scroll-timeline with animations Until now it was possible to parse @scroll-timeline rules, but they did not actually do anything. This CL performs the necessary integration into StyleEngine and CSSAnimations (partially) to make something happen. The applicable StyleRuleScrollTimeline objects are maintained on StyleEngine. When calculating the animation update, we now take the animation-timeline property into account, and look for a rule on StyleEngine corresponding to the specified timeline name. This rule (if found) then causes a new ScrollTimeline to be created. This is by no means a fully functional implementation, but it's a start. The most notable omission is updating timelines, which is currently not possible (crbug.com/1097053). Other omissions, flaws, or postponed work are either tracked as bugs (with TODOs that reference them) or as failing expectations. This ensures that we don't miss anything before shipping. Bug: 1074052 Change-Id: I04e75be1dc970ed2f542e60457f8db25bbb0fe7a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253752 Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by: Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#787258} -- wpt-commits: 5fff9da6c050f3d6a9a3d8bc9d9eff6308826e12 wpt-pr: 24252
afd90cc4ac1e61d262bd13e36309697fcb3ee5ee: Bug 1639897 [wpt PR 23727] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 10 Jul 2020 15:48:57 +0000 - rev 541058
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1639897 [wpt PR 23727] - Update wpt metadata, a=testonly wpt-pr: 23727 wpt-type: metadata
db041398ba02897fc9d4f54ac39825802e529b64: Bug 1639897 [wpt PR 23727] - Clipboard API: Implement clipboard-read and clipboard-write Feature Policy., a=testonly
Darwin Huang <huangdarwin@chromium.org> - Fri, 17 Jul 2020 11:14:36 +0000 - rev 541057
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1639897 [wpt PR 23727] - Clipboard API: Implement clipboard-read and clipboard-write Feature Policy., a=testonly Automatic update from web-platform-tests Clipboard API: Implement clipboard-read and clipboard-write Feature Policy. Complete and expose previously incomplete feature policy integration. Also, use separate clipboard-read and clipboard-write feature policies, as opposed to the previous single clipboard feature policy. Previously, https://crrev.com/c/1913466 aimed to add Feature Policy integration to the Clipboard API. Unfortunately, this integration wasn't complete, so sites didn't have the option to allow cross-origin iframes to access the clipboard at all after this change. Complete the integration to allow sites to enable this feature policy. Also, as feature and permission policies are being merged, use clipboard-read and clipboard-write as feature policy names, so that the feature policy and permission names match. Verified by via automated WPTs, and also manually tested by running this example[1], which fails without this CL, and succeeds with the CL. Intent to prototype and ship: https://groups.google.com/a/chromium.org/d/msg/blink-dev/IDAapW6w4to/iSH1MXRFCgAJ [1]: https://smart-flicker-baroness.glitch.me/ Bug: 1074489 Change-Id: I09125d74510ed6c868d84936df595d02326619b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2164248 Commit-Queue: Darwin Huang <huangdarwin@chromium.org> Reviewed-by: Alex Russell <slightlyoff@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Ian Clelland <iclelland@chromium.org> Reviewed-by: Balazs Engedy <engedy@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#786914} -- wpt-commits: e2ebd58e4c8071639d939f6dba26ff5e8e7a8084 wpt-pr: 23727
274469b59caca32e02ccb04b668b5418ac3f8c4f: Bug 1651809 [wpt PR 24540] - Cleanup newline-removal in manifest_build.py, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Fri, 17 Jul 2020 11:14:30 +0000 - rev 541056
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651809 [wpt PR 24540] - Cleanup newline-removal in manifest_build.py, a=testonly Automatic update from web-platform-tests Cleanup newline-removal in manifest_build.py (#24540) This is a small follow-up to d7423b4ef835ac579b2aa6cbd0e88e47ed1c82cd, which was an attempt at a hotfix that turned out to be the problem. To tidy up the code, trim the sha at retrieval time and don't trim the tag (which turned out not to have a newline in it). -- wpt-commits: 7b2f44248d9955dd11663479a469926969c8884e wpt-pr: 24540
2a5a08c03998cb4bf66b05d6e776bcb97143cfa6: Bug 1651870 [wpt PR 24548] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 10 Jul 2020 13:51:11 +0000 - rev 541055
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651870 [wpt PR 24548] - Update wpt metadata, a=testonly wpt-pr: 24548 wpt-type: metadata
e9883c30ee173bd866083dd9659d82c668995170: Bug 1651870 [wpt PR 24548] - Make XRSession.inputSources iterable, a=testonly
Josh Matthews <josh@joshmatthews.net> - Fri, 17 Jul 2020 11:14:22 +0000 - rev 541054
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651870 [wpt PR 24548] - Make XRSession.inputSources iterable, a=testonly Automatic update from web-platform-tests dom: Generate iterator symbol for interfaces with indexed getters. -- wpt-commits: c114ff9b2f781a671261d55ca977075d084a7ebf wpt-pr: 24548
71863acfbb62ec7aa87e43111a8fc83d31437562: Bug 1650764 [wpt PR 24454] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 10 Jul 2020 13:12:32 +0000 - rev 541053
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1650764 [wpt PR 24454] - Update wpt metadata, a=testonly wpt-pr: 24454 wpt-type: metadata
b33f9acf32601547cc33d2f7b810283533642887: Bug 1650764 [wpt PR 24454] - Construct StyleResolver in StyleEngine constructor., a=testonly
Rune Lillesveen <futhark@chromium.org> - Fri, 17 Jul 2020 11:14:14 +0000 - rev 541052
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1650764 [wpt PR 24454] - Construct StyleResolver in StyleEngine constructor., a=testonly Automatic update from web-platform-tests Construct StyleResolver in StyleEngine constructor. Years ago, the StyleResolver was deleted and re-created for certain style sheet changes. The current lifetime of the StyleResolver is that it is created once on first EnsureStyleResolver and only freed when the StyleEngine is disposed. Instead of checking if it needs to be constructed every time we access it, create it as part of constructing the StyleEngine. We don't create it for documents without a Frame for which we should not use the StyleResolver. Change-Id: I1f1d2ef322d2599737f584191550f769dcf6828e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2270209 Commit-Queue: Rune Lillesveen <futhark@chromium.org> Reviewed-by: Robert Flack <flackr@chromium.org> Reviewed-by: Majid Valipour <majidvp@chromium.org> Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#787158} -- wpt-commits: bfe92da84ad0ab55f1ee333f64bd5860e6da5ff5 wpt-pr: 24454
7ab479464d58b43448615790b51a66ed0c80c3f8: Bug 1649709 [wpt PR 24409] - Python 3: port webappapis and cross-origin tests in html, a=testonly
ziransun <zsun@igalia.com> - Fri, 17 Jul 2020 11:14:09 +0000 - rev 541051
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1649709 [wpt PR 24409] - Python 3: port webappapis and cross-origin tests in html, a=testonly Automatic update from web-platform-tests Python 3: port webappapis and cross-origin tests in html (#24409) * Python 3: port webappapis and cross-origin tests in html * Correct use of type on name argument for uuid5 -- wpt-commits: c44d7e9b7dbdecfe831e0feca8bd5ffcd02d424a wpt-pr: 24409
3f00e2e3ba95bf4fffb05409167a8231fa573f58: Bug 1646440 [wpt PR 24202] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 10 Jul 2020 11:56:12 +0000 - rev 541050
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1646440 [wpt PR 24202] - Update wpt metadata, a=testonly wpt-pr: 24202 wpt-type: metadata
b64fd952b0299562a7b70792a114ece725719e20: Bug 1646440 [wpt PR 24202] - Add interfaces/intervention-reporting.idl and test, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Fri, 17 Jul 2020 11:14:01 +0000 - rev 541049
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1646440 [wpt PR 24202] - Add interfaces/intervention-reporting.idl and test, a=testonly Automatic update from web-platform-tests Add interfaces/intervention-reporting.idl and test (#24202) Closes https://github.com/web-platform-tests/wpt/pull/24193 -- wpt-commits: cce62117eaefe78cf0a1bcb858c2b535ec5d2e0b wpt-pr: 24202
b9a0dcc23e3a5f4f302d37b556361cead36830f3: Bug 1651562 [wpt PR 24527] - [FlexNG] Fix % max-height definiteness, a=testonly
David Grogan <dgrogan@chromium.org> - Fri, 17 Jul 2020 11:13:52 +0000 - rev 541048
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651562 [wpt PR 24527] - [FlexNG] Fix % max-height definiteness, a=testonly Automatic update from web-platform-tests [FlexNG] Fix % max-height definiteness A replaced element's % max-height was being ignored when it was the child of a flex item that acquired its definite height by stretching. This was flaky though, it only broke when the image was loaded before the flexbox had laid out. If the flexbox was laid out, _then_ the image loaded and hence caused a relayout, the image would obey the definiteness that was cached from the flex item's first layout. Change-Id: I2b429aed111a1b800311287337f951c15fcc72f2 Fixed: 1092934 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2287370 Commit-Queue: David Grogan <dgrogan@chromium.org> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#787095} -- wpt-commits: 8e1b09f5bdecd4e9709e2377d4344acef5f9002c wpt-pr: 24527
0dc152dfee0a1e863843ef1b66ac82350cdd67cc: Bug 1651866 [wpt PR 24547] - [NativeFS] Update some tests to getFooHandle., a=testonly
Marijn Kruisselbrink <mek@chromium.org> - Fri, 17 Jul 2020 11:13:46 +0000 - rev 541047
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651866 [wpt PR 24547] - [NativeFS] Update some tests to getFooHandle., a=testonly Automatic update from web-platform-tests [NativeFS] Update some tests to getFooHandle. http://crrev.com/c/2285670 renamed getFile/getDirectory to getFileHandle and getDirectoryHandle, this updates some tests that were missed in that change. Bug: 1103022 Change-Id: Id4b4a60677424cae59af7626e57acc1f6be4bd29 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2291252 Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org> Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/master@{#787072} -- wpt-commits: 319817182b307f3a1637dfddc25d44eb6262a71c wpt-pr: 24547
34e8f436aed2585104f338917c8a60111f6725f5: Bug 1651873 [wpt PR 24550] - Re-add paint_invalidation_container in PrePaintTreeWalk., a=testonly
Chris Harrelson <chrishtr@chromium.org> - Fri, 17 Jul 2020 11:13:41 +0000 - rev 541046
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651873 [wpt PR 24550] - Re-add paint_invalidation_container in PrePaintTreeWalk., a=testonly Automatic update from web-platform-tests Re-add paint_invalidation_container in PrePaintTreeWalk. This is needed in order to make sure to call SetNeedsCheckRasterInvalidation() on all GraphicsLayers that need raster invalidation after an invalidation of paint. To do this involves finding out into which GraphicsLayer a LayoutObject paints. We'll be able to remove it in favor of a dirty bit on CompositingLayerAssigner when pre-paint is moved before compositing. Bug: 1102733 Change-Id: I506d7e574e802502d9414ad67f14f0d4c072b184 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2290547 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Auto-Submit: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#787058} -- wpt-commits: e67f139c7c1bc14c85c7def4db56e3a1964624d1 wpt-pr: 24550
280e4502e83273310e1baf6aa94bd9eee4e2f649: Bug 1651853 [wpt PR 24543] - [NativeFS] Add kind enum to replace isFile/isDirectory., a=testonly
Marijn Kruisselbrink <mek@chromium.org> - Fri, 17 Jul 2020 11:13:36 +0000 - rev 541045
Push 37613 by btara@mozilla.com at Sat, 18 Jul 2020 09:26:25 +0000
Bug 1651853 [wpt PR 24543] - [NativeFS] Add kind enum to replace isFile/isDirectory., a=testonly Automatic update from web-platform-tests [NativeFS] Add kind enum to replace isFile/isDirectory. Following changes in https://github.com/WICG/native-file-system/pull/198 Bug: 1103841 Change-Id: I4c67d6eb6cf605bb10d4ace83594900bfe1157ad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2290535 Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#787046} -- wpt-commits: 48dce4661e20f18a75440e961b6a5cd51fac19fd wpt-pr: 24543
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip