0b6c9041425cc478d6828edc7146db6b677f94e7: Bug 1464338 [wpt PR 11159] - Avoid using template string in testharness.js, a=testonly
Simon Pieters <zcorpan@gmail.com> - Wed, 06 Jun 2018 14:52:36 +0000 - rev 422153
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1464338 [wpt PR 11159] - Avoid using template string in testharness.js, a=testonly Automatic update from web-platform-testsAvoid using template string in testharness.js This is to make it work in older browsers. -- wpt-commits: 7d24703c720f08f472319a7af2ef5bc6dec25346 wpt-pr: 11159
f41374897ca8a132f34a1a3d0ea16d04461f2f47: Bug 1464320 [wpt PR 11011] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 25 May 2018 06:31:50 +0000 - rev 422152
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1464320 [wpt PR 11011] - Update wpt metadata, a=testonly wpt-pr: 11011 wpt-type: metadata
85d401e121224b10987c798b0e4fb07549c5de24: Bug 1464320 [wpt PR 11011] - Parameterize domain and port references, a=testonly
Mike Pennisi <mike@mikepennisi.com> - Wed, 06 Jun 2018 14:51:11 +0000 - rev 422151
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1464320 [wpt PR 11011] - Parameterize domain and port references, a=testonly Automatic update from web-platform-testsParameterize domain references The web-platform-tests server may be configured to run from any host name. It offers a text substitution feature so that tests can be written to account for this variability. Update tests which previously referenced the default host name (`web-platform.test`) to instead reference a parameterized value. -- [csp] Parameterize port references The web-platform-tests server may be configured to run from any TCP/IP port. It offers a text substitution feature so that tests can be written to account for this variability. Update tests which previously referenced a static port number to instead reference a parameterized value. -- wpt-commits: ad2e6b7a5a3049bfcdfdd186fb5bf922c3506bf9, ca8f405403de184b168b6bbdbba1d24504f4afd9 wpt-pr: 11011
59dab3cb67fadfa80a3fe08eb5313ba0f9fb38e0: Bug 1457328 [wpt PR 10670] - Cleanup plugin element frames when the layout tree is detached, a=testonly
Ehsan Karamad <ekaramad@chromium.org> - Wed, 06 Jun 2018 14:49:44 +0000 - rev 422150
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1457328 [wpt PR 10670] - Cleanup plugin element frames when the layout tree is detached, a=testonly Automatic update from web-platform-testsCleanup plugin element frames when the layout tree is detached Unlike frames, plugin elements (<embed> and <object>) are updated when their layout tree is rebuilt. However, due to an oversight, <embed> or <object> elements displaying subframes would only have the associated content view (FrameView) torn down, leaving a dangling content frame. This led to some interesting side effects: - When transitioning from a local frame to a plugin, the content frame would remain live, with JS still happily running. - When transitioning from a remote frame to a plugin, - When navigating a remote frame from one URL to another, the element would stop updating since the FrameView would be torn down but a new one would never be created. Note that this was not (as much of) a problem for local frames, since local frames re-create the LocalFrameView on every navigation. With this CL, if a plugin element has an associated content frame, use that to clean up the state associated with the element when the layout tree is detached. This can cause the browser context to be re-created: this matches the behavior of Edge and Firefox. Note that there is still one edge case where Blink behaves oddly: if the navigation fails and should display fallback content, the content frame still remains attached. This will be addressed in followups. Link to whatwg issue: https://github.com/whatwg/html/issues/3576 Bug: 776510, 781880 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: Id18605fbe602ea6c0076c1d579345cdcf28cc984 Reviewed-on: https://chromium-review.googlesource.com/996314 Commit-Queue: Ehsan Karamad <ekaramad@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#561768} -- wpt-commits: 3391fa43ca730a80b6939476086fafd9ec884ff1 wpt-pr: 10670
f9f09e6c50ed8275e030439d0d89551bce1e9a61: Bug 1463628 [wpt PR 11114] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 23 May 2018 02:39:03 +0000 - rev 422149
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1463628 [wpt PR 11114] - Update wpt metadata, a=testonly wpt-pr: 11114 wpt-type: metadata
b8097a5e336b0f018be678af7b0ec5138f6af1ca: Bug 1463628 [wpt PR 11114] - Refactor :focus-visible implementation, a=testonly
Alice Boxhall <aboxhall@chromium.org> - Wed, 06 Jun 2018 14:48:20 +0000 - rev 422148
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1463628 [wpt PR 11114] - Refactor :focus-visible implementation, a=testonly Automatic update from web-platform-testsRefactor :focus-visible implementation - Rename "ShouldShowFocusRingOnMouseFocus" to "MayTriggerVirtualKeyboard" - Remove UserActionElementSet::WasFocusedByMouse() and replace with Document::LastFocusType() - Move WillCallDefaultEventHandler() implementation, which checks whether the most recent event was from the keyboard and forces style recalculation if one has occurred, up to Node from HTMLFormControlElement - Tracks HadKeyboardEvent() on Document as well - Adds many more tests for the existing :focus-visible behaviour This lays the groundwork for some future changes: - Triggering :focus-visible matching on keyboard events when an element is already focused - Potentially moving the default focus ring drawing logic out of LayoutTheme and delegating to the :focus-visible matching logic instead. Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I5dc0a00c9068dc16bcd36a1c52c706646378ca50 Reviewed-on: https://chromium-review.googlesource.com/1060717 Commit-Queue: Alice Boxhall <aboxhall@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#561746} -- wpt-commits: 5057b3cee61ca468cd4e8247ea59f5c7d323aa82 wpt-pr: 11114
6801a998b9dd4e159b80a4f3ab47e007e27de695: Bug 1463510 [wpt PR 11104] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 05 Jun 2018 14:31:15 +0000 - rev 422147
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1463510 [wpt PR 11104] - Update wpt metadata, a=testonly wpt-pr: 11104 wpt-type: metadata
4974dd754e87bd571438ea2d2881f60e711494b1: Bug 1463510 [wpt PR 11104] - Fix race condition in frameElement.html., a=testonly
arthursonzogni <arthursonzogni@chromium.org> - Wed, 06 Jun 2018 14:46:58 +0000 - rev 422146
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1463510 [wpt PR 11104] - Fix race condition in frameElement.html., a=testonly Automatic update from web-platform-testsFix race condition in frameElement.html. I am working on https://crbug.com/831155. Some tests that are relying on how things are scheduled in Blink are failing. There was a race condition in this test. The iframe "#fr2" was asked to navigate to a first URL, but soon after, a javascript function modifies the iframe.src to navigate elsewhere. What happened when it didn't work? 1) The first navigation starts. 2) The second navigation is scheduled (See blink's NavigationScheduler) 3) The first navigation commits. FrameLoader::CommitProvisionalLoad() executes: frame_->GetNavigationScheduler().Cancel(). It cancels the second navigation. This CL fixes the race condition. Bug: 831155 Change-Id: I2dd951140b4c5a671c749348ca0247f1901d8b77 Reviewed-on: https://chromium-review.googlesource.com/1069013 Commit-Queue: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#561659} -- wpt-commits: a89693b62066da0e4808c0bc76c581188398e73d wpt-pr: 11104
f89c4982a46dd8111c3463d6efb5c566c46708fa: Bug 1463607 [wpt PR 11107] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 22 May 2018 23:34:53 +0000 - rev 422145
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1463607 [wpt PR 11107] - Update wpt metadata, a=testonly wpt-pr: 11107 wpt-type: metadata
475c97311490ef44bf30b09b547f8451e45b4c19: Bug 1463607 [wpt PR 11107] - [css-layout-api] Adds ability to set available sizes on children., a=testonly
Ian Kilpatrick <ikilpatrick@chromium.org> - Wed, 06 Jun 2018 14:45:31 +0000 - rev 422144
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1463607 [wpt PR 11107] - [css-layout-api] Adds ability to set available sizes on children., a=testonly Automatic update from web-platform-tests[css-layout-api] Adds ability to set available sizes on children. This adds the availableInlineSize, availableBlockSize, to the layout constriants options dictionary. This also makes the children "shrink-to-fit" if they are inside a custom layout pass. Additional logic was needed to *not* "shrink-to-fit" children during the layout fallback if any occurred, so LayoutCustomPhaseScope was added to handle this. The tests that were added test a new BFC with inline children to see if shrink to fitting works as expected. Bug: 726125 Change-Id: Ic86d51579b680d871c66040f54e532bc47d79979 Reviewed-on: https://chromium-review.googlesource.com/1069252 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#561602} -- wpt-commits: 127a32efa15d361e0eb4d0db1cbf5a99d26d72d9 wpt-pr: 11107
2128a7016bf665cf106a8fd143c0871a16c4aa9d: Bug 1464104 [wpt PR 11141] - Fix wpt/css/css-masking/parsing/clip-valid.html subtest, a=testonly
Fredrik Söderquist <fs@opera.com> - Wed, 06 Jun 2018 14:44:04 +0000 - rev 422143
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1464104 [wpt PR 11141] - Fix wpt/css/css-masking/parsing/clip-valid.html subtest, a=testonly Automatic update from web-platform-testsFix wpt/css/css-masking/parsing/clip-valid.html subtest Percentages are not allowed in rect() (arguments are '<length> | auto'.) Move the old test to clip-invalid.html and replace it with one that doesn't use percentages. Bug: 843084 Change-Id: I3cadd99da0d302ac5a0cd012450dd7ade233681c Reviewed-on: https://chromium-review.googlesource.com/1071469 Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Reviewed-by: Eric Willigers <ericwilligers@chromium.org> Cr-Commit-Position: refs/heads/master@{#561598} -- wpt-commits: d2db9cd1bfe4a2b5aa5d33d4b11b50d2332ecc9b wpt-pr: 11141
1389f6e0eaad9bafadc94cf8dbf99c64c90ed210: Bug 1464200 [wpt PR 11148] - Run apt-get update before installing Chrome, a=testonly
Geoffrey Sneddon <me@gsnedders.com> - Wed, 06 Jun 2018 14:42:50 +0000 - rev 422142
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1464200 [wpt PR 11148] - Run apt-get update before installing Chrome, a=testonly Automatic update from web-platform-testsRun apt-get update before installing Chrome There might have been new package releases since the Docker image was built, and the old packages may no longer exist on the mirror; therefore, update the package lists before installing Chrome. -- wpt-commits: a8a5dc635dc73e3ebb10c1162bc3488bfec6ea4d wpt-pr: 11148
97f7cbe0e2bf60d56049e19d533817effce109be: Bug 1463828 [wpt PR 11127] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 25 May 2018 19:26:02 +0000 - rev 422141
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1463828 [wpt PR 11127] - Update wpt metadata, a=testonly wpt-pr: 11127 wpt-type: metadata
e48ad277fdd99ce7a703327e495acf1e3808fd88: Bug 1463828 [wpt PR 11127] - Add new tests for RAF and Canvas commit on Workers, a=testonly
Fernando Serboncini <fserb@chromium.org> - Wed, 06 Jun 2018 14:41:25 +0000 - rev 422140
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1463828 [wpt PR 11127] - Add new tests for RAF and Canvas commit on Workers, a=testonly Automatic update from web-platform-testsAdd new tests for RAF and Canvas commit on Workers Bug: 563816 Change-Id: I22d22fcd06d6bbb9de94dc891fb4b4f327720881 Reviewed-on: https://chromium-review.googlesource.com/1070210 Commit-Queue: Fernando Serboncini <fserb@chromium.org> Reviewed-by: Justin Novosad <junov@chromium.org> Cr-Commit-Position: refs/heads/master@{#561573} -- wpt-commits: 3fa1c7685bc47e1fb4d6fcfae74d0401c5077436 wpt-pr: 11127
1574da368c4664653a37789612df98cbb9f5b87a: Bug 1463067 [wpt PR 11088] - Add async-local-storage/OWNERS, a=testonly
Simon Pieters <zcorpan@gmail.com> - Wed, 06 Jun 2018 14:40:09 +0000 - rev 422139
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1463067 [wpt PR 11088] - Add async-local-storage/OWNERS, a=testonly Automatic update from web-platform-testsAdd async-local-storage/OWNERS -- wpt-commits: 1302c1cd37d414d365b5ef4fd387392afb7e36af wpt-pr: 11088
02fbaf75ceee2610a1c8baa42556b67d8f49e507: Bug 1464035 [wpt PR 11136] - Add regression test for ::first-line breaking ::placeholder styles, a=testonly
Chris Nardi <cnardi@chromium.org> - Wed, 06 Jun 2018 14:38:40 +0000 - rev 422138
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1464035 [wpt PR 11136] - Add regression test for ::first-line breaking ::placeholder styles, a=testonly Automatic update from web-platform-testsAdd regression test for ::first-line breaking ::placeholder styles A bug was reported where ::first-line broke ::placeholder styling, which seems to have been fixed in https://crrev.com/550589. However, we don't currently have a test for this bug. Add in a test to make sure we don't regress with this bug. Bug: 806247 Change-Id: I5bbcda1ccf5b3ea08a7b66a68071a802f42e9228 Reviewed-on: https://chromium-review.googlesource.com/1071126 Commit-Queue: Chris Nardi <cnardi@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#561526} -- wpt-commits: a381d5590bd6793152ec87c3f195f4bb83550792 wpt-pr: 11136
ecb5e6f5a4a8db0dbae918ef46100ce75085ed5e: Bug 1463623 [wpt PR 11111] - Remove desiredCapabilities, a=testonly
Clay Martin <clmartin@microsoft.com> - Wed, 06 Jun 2018 14:37:26 +0000 - rev 422137
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1463623 [wpt PR 11111] - Remove desiredCapabilities, a=testonly Automatic update from web-platform-testsRemove desiredCapabilities -- wpt-commits: 9fce1e8be186d615b83b6e5cedfeed2dbb0f16f3 wpt-pr: 11111
74e96b7119d78d2426038a0f89f33a396f4da7b3: Bug 1462683 [wpt PR 11071] - Move taskcluster to dedicated wpt worker type, a=testonly
James Graham <james@hoppipolla.co.uk> - Wed, 06 Jun 2018 14:36:12 +0000 - rev 422136
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1462683 [wpt PR 11071] - Move taskcluster to dedicated wpt worker type, a=testonly Automatic update from web-platform-testsSwitch to dedicated wpt taskgroup in taskcluster -- wpt-commits: 24811101f05b1956a19d465891f3c386c95bf939 wpt-pr: 11071
37ffa67c86d1f9f8899bf56234602aa5c99db611: Bug 1463063 [wpt PR 11087] - Add keyboard-map/OWNERS, a=testonly
Simon Pieters <zcorpan@gmail.com> - Wed, 06 Jun 2018 14:34:56 +0000 - rev 422135
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1463063 [wpt PR 11087] - Add keyboard-map/OWNERS, a=testonly Automatic update from web-platform-testsAdd keyboard-map/OWNERS -- wpt-commits: 6554296ca8cb3de37a35fe2782aedfe0e02d2750 wpt-pr: 11087
019681d3ab4fedcc78b4dc153ec2a778e9c091c1: Bug 1463155 [wpt PR 11094] - Add a warning about trusting the root CA, a=testonly
jgraham <james@hoppipolla.co.uk> - Wed, 06 Jun 2018 14:33:39 +0000 - rev 422134
Push 34122 by ebalazs@mozilla.com at Mon, 11 Jun 2018 09:37:00 +0000
Bug 1463155 [wpt PR 11094] - Add a warning about trusting the root CA, a=testonly Automatic update from web-platform-testsAdd a warning about trusting the root CA (#11094) -- wpt-commits: 5d4f7853b9ae10fe7f4e0321b656ee7afb54aeb3 wpt-pr: 11094
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip