I wanted to fix the more general problem and script-block more of
FlushPendingNotifications, but simple attempts to do that have resulted in
terribly orange try runs with very bizarre failures, so in the "perfect is the
enemy of good" spirit, fix the issue at hand (scroll anchoring adjustments not
dealing with layout reentering beneath them) by running them while
script-blocked, which is the right thing to do anyway.
Differential Revision: https://phabricator.services.mozilla.com/D47256
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Add missing worklet referrer tests
This CL adds more web-platform-tests for the `Referer` on worklet
descendant requests. This CL introduces tests where we fetch a
same-origin descendant script from a cross-origin worklet script served
with varying referrer policies.
The tests are similar to those introduced in crrev.com/c/1809205 for
module scripts, and will pass once crrev.com/c/1808663 is merged.
R=ikilpatrick@chromium.org, kouhei@chromium.org
Bug: 786862,1004083
Change-Id: I4425be4264424b52e4ec307513a404541869f2a1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1813122
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699351}
--
Add long timeout to worklet referrer tests
They take close to 10 seconds on Firefox:
https://github.com/web-platform-tests/wpt/pull/19165#issuecomment-534985874
--
wpt-commits: 98c89472a9e6359bfac5b40b05188c9c5b39be79, eaa551911f12c5c526f56cafd0c7ab24667ead3c
wpt-pr: 19165
Automatic update from web-platform-tests
Don't fold SaveAlphaLayer into DrawTextBlob
SkPaint::drawTextBlob applies alpha on each individual glyph, so
we should keep SaveAlphaLayer to ensure the alpha is applied atomically
on the whole text blob.
Bug: 1006140
Change-Id: I8b1d1868a3423ed4f0ef6541cc8db354773dfb24
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1821944
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699621}
--
Use /fonts/ahem.css to pass lint
--
wpt-commits: 2805a5a862f54b9c5458f9fc8e73d5e51fb6220e, 7b3ea483aabbbc65dda011e6d4cfc35086338706
wpt-pr: 19260
Automatic update from web-platform-tests
Ensure documents with no TopFrameOrigin correctly handle hasStorageAccess calls.
In some scenarios a document's TopFrameOrigin may be empty. This change ensures
that this case is handled correctly during hasStorageAccess() calls.
Bug: 1005778
Change-Id: Ic00cf3fcca143e83e277ca43835480c8d31536ed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1814726
Commit-Queue: Brandon Maslen <brandm@microsoft.com>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699602}
--
wpt-commits: d320b984d726cf4fd3c540f96adb072df03346d3
wpt-pr: 19281
Automatic update from web-platform-tests
Add AutoClearOverrideLogical{Width,Height}
This is a bit safer than the manual calling of clear and set.
This also adds the test from https://crrev.com/c/1808498 to trunk/wpt.
Bug: 1002899
Change-Id: I2a4963fc08f1b66a0d9cdaf63f1d263715f97178
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1810238
Auto-Submit: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699563}
--
wpt-commits: b54ab49624cfb1bc3956c6518f683d0b0c38b681
wpt-pr: 19127
Automatic update from web-platform-tests
[NativeFS] Refactor WPT tests to support native FS as well.
Also changes the sandboxed file system version of these tests to run in
both windows and workers.
The native file system version of these tests are currently manual tests.
In the future we can automate them. Also currently some of the writer
tests don't pass in the native file system version, because of things like
bug 998913.
Bug: 998917
Change-Id: I4aefee6e35008afd73c2cf316d16ea189717bd4b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1787869
Reviewed-by: Olivier Yiptong <oyiptong@chromium.org>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699539}
--
wpt-commits: e7b232f535cf1ebd0026bd66d1ff3bf096744862
wpt-pr: 18883
Automatic update from web-platform-tests
Fix xrWebGLLayer_constructor test
xrWebGLLayer_constructor was mistakenly updated to require user
activation though the spec does not explicitly require it in this case
since the inline session does not request any features. Even were it
to require this, the way that it was structured caused there to not be
a promise set when the ".then" was caused, giving a script error.
This change essentially reverts WPT Commit 16d4388, and was discussed
with Mozilla when deciding which way to fix it.
Bug: 1007304
Change-Id: I824f63cb172aed5928c55224b31c00803b5ddaa2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1822821
Commit-Queue: Jacob DeWitt <jacde@chromium.org>
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Auto-Submit: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Jacob DeWitt <jacde@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699467}
--
wpt-commits: 75515ddfc56f2228ea9444f61f24cd78eba16aa6
wpt-pr: 19267
Automatic update from web-platform-tests
Added support for navigation-controls media query
This change adds support for navigation-controls media feature,
which will initially be used to detect if the user agent supplies a
back button present in its UI. This media feature will allow apps to
avoid the "double back button" problem by letting them conditionally
display a back button depending on whether the user agent is already
displaying one.
The logic for updating navigation-controls from its default state
has not yet been implemented.
Spec: https://github.com/fallaciousreasoning/backbutton-mediaquery
Bug: 822944
Change-Id: If8bc5054c0591f7e822277a83119273b69aef0c9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1802195
Commit-Queue: Mustapha Jaber <mustjab@microsoft.com>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699459}
--
wpt-commits: aea25956a4ab771261d6324e105893faa013e62c
wpt-pr: 19091
Automatic update from web-platform-tests
Correctly support `Sec-Fetch-Mode` for `<portal>` requests.
Requests from `<portal>` elements currently send a `Sec-Fetch-Mode` of
`navigation`. They ought to send something more like
`nested-navigation`, which more accurately represents the request's
status vis-a-vis its requestor.
https://github.com/w3c/webappsec-fetch-metadata/issues/46
Bug: 1005143
Change-Id: Ib7f434ddf90d2e15b4bf139ab77c778a090251f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1819297
Reviewed-by: Lucas Gadani <lfg@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Alex Moshchuk <alexmos@chromium.org>
Auto-Submit: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699399}
--
wpt-commits: 3bff4fcbad687be221f6830969fe4f7086ce2cf8
wpt-pr: 19217
Automatic update from web-platform-tests
[LayoutNG] Allow floats to be placed "before" other floats of the same type.
Floats have some "interesting" behaviour which allows a left (or right)
float to be placed left (or right) of a previous float. This typically
isn't allowed.
This occurs when a float has "negative size" e.g. it has a large
negative margin, which is larger than its width. E.g.
<div style="width: 50px; margin-left: -150px; float: left;"></div>
In such cases the float doesn't respect the normal rules, and is
placed in a typically invalid area.
This patch also changes "const LogicalSize& minimum_size" to
"const LayoutUnit minimum_inline_size" for "FindLayoutOpportunity".
Bug: 1005437
Change-Id: I4c91a53911b2651346487f71c4b31ec6e0240202
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1819356
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#699390}
--
wpt-commits: 38028a8b9d38b369952c27f5b5addc2ef5b5bff9
wpt-pr: 19235
Automatic update from web-platform-tests
Restrict 'keySplines' x-values to the [0, 1] range
Per SMIL[1], all the values in a key spline should be within [0, 1], but
to be consistent with CSS' timing function, allow y-values to be outside
that range (at least for now).
While in ParseKeySplinesInternal(...), rename the |pos_*| local
variables to something that carries a little bit more semantic meaning.
[1] https://www.w3.org/TR/SMIL3/smil-animation.html#adef-keySplines
Bug: 1006544
Change-Id: I6baa4085943eca8144605fb0a5c442bc8486ad87
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1821158
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#699373}
--
wpt-commits: 42753d6fecd3c1c8463d723aa49a89e0dc2616bf
wpt-pr: 19248
