Unicode property escapes allow regexps to match based on Unicode properties. Some of the test262 tests are quite large and slow, especially in the arm64 simulator: on my local machine, tests that took 1.7 seconds in native builds timed out after 150 seconds when simulated. This patch turns them off for arm64-simulator builds.
(V8 has encountered similar issues: d4ddf645c3/test/test262/test262.status (L768-L771))
Differential Revision: https://phabricator.services.mozilla.com/D73764
The cross-realm tests don't work with --more-compartments enabled. Now that the dotAll version of this test is enabled, it has to be added to the list.
Differential Revision: https://phabricator.services.mozilla.com/D73762
If we don't do this, configure will happily think the linker kind is
"unknown", which then causes problems downstream.
Differential Revision: https://phabricator.services.mozilla.com/D75300
We already ensure that we finish our write before doing a fast
shutdown, but right now there's just too much noise in the late
write checking telemetry because of this.
Differential Revision: https://phabricator.services.mozilla.com/D75389
Automatic update from web-platform-tests
[Security][Coop] Use COOP only if this is top level
COOP is used only in top level document, and COOP headers from iframes
are ignored. This led to an issue in the linked bug, where COOP prevents
a sandboxed iframe to load.
The spec change corresponding to this is under review here:
https://whatpr.org/html/5334/browsing-the-web.html
with this relevant extract:
```
Let navigationCOOP be "unsafe-none".
If browsingContext is a top-level browsing context, then:
Set navigationCOOP to the result of obtaining a cross-origin opener
policy given response and reservedEnvironment.
If sandboxFlags is not empty and navigationCOOP is not "unsafe-none",
then display the inline content with an appropriate error shown to the
user, with the newly created Document object's origin set to a new
opaque origin, run the environment discarding steps for
reservedEnvironment, and return.
```
Bug: 1081169
Change-Id: I2c0b59c84ca52f63436a2312529a4bb0351fff30
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2193771
Commit-Queue: Pâris Meuleman <pmeuleman@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Auto-Submit: Pâris Meuleman <pmeuleman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#767761}
--
wpt-commits: e98a46978594a745b61c70fa3aae84878a081b3b
wpt-pr: 23506
Automatic update from web-platform-tests
Update some scriptlevel tests to match the new syntax. (#23530)
math-script-level-001,003: No longer relevant since there is no computed
values of math-script-level (not a property anymore).
math-script-level-005: This does not correspond to anything in the spec.
math-script-level-002.tentative.html: tweak the test to work with the new syntax.
math-script-level-004.tentative.html: tweak the test to work with the new syntax. Remove the part about the computed values of math-script-level (not a property anymore)
https://github.com/mathml-refresh/mathml/issues/174
--
wpt-commits: fa5b7ba3fee5536abd64b7064320c8fd8da62dd6
wpt-pr: 23530
Automatic update from web-platform-tests
Attribute animations should not be reflected by getAttribute(...)
According to SMIL [1], when an attribute is animated, the actual DOM
attribute should not change. So only synchronize attributes after a base
value change has taken place.
Rename related flags and methods to not include "animated", since that
seems a bit misleading.
Add SVGElement::CollectStyleForAnimatedPresentationAttributes() to
handle animations of attributes that are presentation attributes but are
not actually specified on the target element.
[1] https://www.w3.org/TR/2001/REC-smil-animation-20010904/#BasicAnim
Bug: 735820
Change-Id: I2a0858dd383a1a96e7b96451a6fca07084983d57
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2173184
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#767696}
--
wpt-commits: 31e27f4e968a8e5167889a1a5a3c477a26297455
wpt-pr: 23508
Automatic update from web-platform-tests
Update name in files from Mozilla internship.
These were some files I worked on when I interned at Mozilla using my
personal email address. The author name in the files is out of date.
Change-Id: I5c5a08294676a3c800787bf34fc844d155c9548b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2190978
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Commit-Queue: Sam Bowen <sgbowen@google.com>
Cr-Commit-Position: refs/heads/master@{#767528}
--
wpt-commits: a49081e46a18e439defbd77d18cc5e261d68b215
wpt-pr: 23492
Automatic update from web-platform-tests
Fix computed style for outline-width allowing decimal numbers
Apart from that modified an internal test:
fast/css/round-up-all-line-width-less-than-1-greater-than-0.html
So it actually checks borders too, and removing "pt" values
as the result in pixels might create rounding issues.
BUG=1068107
TEST=external/wpt/css/css-ui/parsing/outline-width-computed.html
Change-Id: I75630b63428fed1dc3fcb91186f059ecddef1e85
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2192931
Commit-Queue: Manuel Rego <rego@igalia.com>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#767417}
--
wpt-commits: 8a489657bc8f0b4a8aac012e3bd2f968080da4a5
wpt-pr: 23498
Automatic update from web-platform-tests
Don't run Fx chaos mode test verification step (#23507)
This makes it more likely that the stability checks timeout and we force merge in spite of any failures. It also doesn't match any other browsers.
--
wpt-commits: b50dcd0324cfcc17facb2e30716130b399a7a6da
wpt-pr: 23507
Automatic update from web-platform-tests
COEP ReportingObserver integration
Notify reports made by COEP to ReportingObservers registered to
documents and service workers.
Support for dedicated workers is blocked on PlzDedicatedWorker.
Support for shared workers is blocked on COEP support for shared
workers.
TESTING:
Now we have two means to test the COEP reporting functionality.
1. Reports sent to the network.
2. Reports observed via ReportingObserver
We need to have *some* tests with both ways, but we don't need to test
all the cases for both ways, and generally speaking ReportingObserver
is easier to use, and less flaky. Hence this CL makes
cache-storage-reporting-*.https.html use ReportingObserver. This CL
also adds reporting-subresource-corp.https.html for subresource loading
cases. I'm planning to make more COEP reporting tests use
ReportingObserver in the future.
Bug: 1052764
Change-Id: Idc670bfc957f05aae813c4a3bce7e361293fc716
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2160291
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#767369}
--
wpt-commits: 540f25e22401fe99e72bf6da2cb1ca1748a8ca4f
wpt-pr: 23288
Automatic update from web-platform-tests
Add lazy load image and iframe referrerpolicy tests
This CL does the following:
- Adds a correct <img loading=lazy referrerpolicy> test, to assert that
the referrerpolicy a deferred image is ultimately fetched with is the
latest one. This is because `referrerpolicy` mutations are considered
relevant mutations as per https://crrev.com/c/2171816 and
https://github.com/whatwg/html/pull/5434, so the latest
referrerpolicy should be honored when an image is fetched after being
deferred.
- Adds an <iframe loading=lazy referrerpolicy> test, to assert that the
referrerpolicy a deferred iframe is fetched with is the
referrerpolicy at parse-time. This is because iframes do not respond
to referrerpolicy mutations, and during spec discussions, it was
mentioned that the request for iframes be set up and finalized at
parse-time. The test is marked tentative because the spec does not
officially exist yet.
- Cleans up an <img loading=lazy crossorigin> test.
Bug: 1080739
Change-Id: I8ec6c344557180721c317f6accaad1b336b39b8c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2185395
Commit-Queue: Dominic Farolino <dom@chromium.org>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#767367}
--
wpt-commits: 2728d5f74309f29be73f7a5a07fe8ba5813bfcd9
wpt-pr: 23490
Automatic update from web-platform-tests
Use tc index for geckodriver downloads
Now we have a dedicated build+package task for geckodriver, we can
download the binaries from there
--
wpt-commits: d8dd60a214e680dee639b7d4be76c2c52f238fd0
wpt-pr: 23502
Automatic update from web-platform-tests
registerProtocolHandler(): handler's URL cannot be a blob URL
For https://github.com/whatwg/html/pull/5530.
--
wpt-commits: 409d25002dbeb39de00ba8d023bb6ac85b7dbfe8
wpt-pr: 23500
Automatic update from web-platform-tests
[FlexNG] Use fragment order as source of truth within simplified layout
Step 3/4 in getting flex to use the simplified layout pass.
We need to use the fragment order as the source or truth as we use the
fragment order as the correct paint order.
The downside of this approach is that we now iterate twice over the
children, once for the fragments, and again for the nodes.
Adding placeholder fragments for the static-positions for the OOF
will fix this.
Bug: 845235
Change-Id: Idb149a25975885cee389c3bae1dd9021dbb5a467
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2187854
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#767208}
--
wpt-commits: 9bbbd9e569e4e5533af0ce55ed4b699b715f7ec6
wpt-pr: 23496
Automatic update from web-platform-tests
[FlexNG] Make simplified layout algorithm use static-position from layer
Step 2/4 in getting flex to use the simplified layout pass.
Instead of re-calculating the static-position within the simplified
layout pass, store this on the paint-layer, and read it back during
the simplified pass.
This isn't ideal. A better way of doing this would be to add
"placeholder" fragments which contain this information instead.
Bug: 845235
Change-Id: I1e8af7f2c487f22c72d657eb1a20b3022329899e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2185513
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#767206}
--
wpt-commits: c313d1fe582d0361f3c2165799e0e4ded109f327
wpt-pr: 23497
Automatic update from web-platform-tests
Update menclose help and explain better how tests work in MathML core (#23495)
No consensus have been reached on the future on menclose so far but this
element has been the source of confusion so the current draft text has
been removed from MathML Core and put in a separate pull request:
https://github.com/mathml-refresh/mathml-core/pull/24
This PR updates the WPT tests accordingly:
* Actual tests for menclose are renamed "tentative" and refer to the
pull request above, so that it becomes clear they are not definitive yet
and browsers are free to ignore them.
* Tests for mrow-like are now referring to MathML3
https://www.w3.org/TR/MathML3/chapter3.html#presm.menclose
They are still valid because unknown elements are treated as mrow-like
in MathML Core.
* Tests for removed legacy features are obviously still valid too.
Again, the documentation is updated to refer to MathML3
https://www.w3.org/TR/MathML3/chapter3.html#presm.menclose
--
wpt-commits: 46b884903ba0153b2cd9d932504f6b88f57614cf
wpt-pr: 23495
Automatic update from web-platform-tests
[FlexNG] Change OverrideHeight variant
In LayoutBox::AvailableLogicalHeightUsing, we were using
OverrideContainingBlockContentLogicalHeight instead of
OverrideContentLogicalHeight for getting the definite height of the flex
item.
Of the new tests, 004.html worked before this fix but it wasn't obvious
that it would.
Bug: 1077524
Change-Id: I2968f8e553476df6fa59c2abb74940eb1467f9cb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2191345
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#767105}
--
wpt-commits: d23d904cc1b805844f232ecde2266b3389da56a0
wpt-pr: 23494
Automatic update from web-platform-tests
[idle] Replace stop() with an AbortSignal
This change replaces the stop() method on IdleDetector with an
AbortSignal provided as an argument to start(). To allow the detector to
be started multiple times the options are now always passed to start()
rather than the constructor. New options replace previously configured
options if specified.
Explainer PR: https://github.com/WICG/idle-detection/issues/19
Bug: 878979
Change-Id: I26418cc3c08a02d77483b7d1b6744c16c17efd08
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2189631
Auto-Submit: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Ayu Ishii <ayui@chromium.org>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#767018}
--
wpt-commits: dc329e1a648b156a9c0191357f39344a2a28a037
wpt-pr: 23472
Automatic update from web-platform-tests
[AspectRatio] Handle min-block-size: auto for aspect ratio
For the default min-height/width, aspect-ratio should only be the minimum
size, and the resulting block size should grow to fit all the content:
https://drafts.csswg.org/css-sizing-4/#aspect-ratio-minimum
Bug: 1045668
Change-Id: I06385087d778e7f05e7097dc25d6858397d0c0e1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2186076
Auto-Submit: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#767012}
--
wpt-commits: 0e87b71ad6e6951b22586dce491f7ee1cf698e46
wpt-pr: 23469
Automatic update from web-platform-tests
Mark two idlharness.html tests as timeout=long
These are symptomatic of crbug.com/1047818, but to stop the pain for
sheriffs lets mark them timeout=long for now.
Bug: 1079238, 1080608
Change-Id: I71e2ce51e4a6807dcdea54765ff9c96afbf2696d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2191076
Reviewed-by: Robert Ma <robertma@chromium.org>
Commit-Queue: Robert Ma <robertma@chromium.org>
Auto-Submit: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#766994}
--
wpt-commits: b0f0a12c732142dfa2b4933a1d3ec44a4a88a841
wpt-pr: 23491
Automatic update from web-platform-tests
device orientation: Try to remove flakiness from tests.
https://crrev.com/c/2154389 ("[device-orientation] Simplifies tests by using
EventWatcher") ended up introducing some Chromium-specific flakiness to most
tests that started using EventWatcher, and the Mac bots in particular seem
to trigger this flakiness very often.
This comes from the fact that EventWatcher will continue watching for events
until the end of the test, and the Blink implementation of the
DeviceOrientation Event specification ends up emitting a non-standard null
event whenever there are no more events to send. This event can end up being
caught by EventWatcher, which correctly reports it as unexpected.
For now, replace most usages of EventWatcher with a much simplified version
of the waitForEvent() function removed in the CL above that only subscribes
to events once.
Bug: 816462, 1078298
Change-Id: I181219f2be19bba8a392c2bf64373f01df46c398
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2190273
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Auto-Submit: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Cr-Commit-Position: refs/heads/master@{#766988}
--
wpt-commits: 54b6be43d7c1be3393ddf921703e60dee74e7777
wpt-pr: 23481
Automatic update from web-platform-tests
Fugu: Add a permission for Screen Enumeration & Window Placement
Add WINDOW_PLACEMENT content setting and permission enum values.
Use this to gate access to the window.getScreens() experimental API.
Wire up the permission request dialog and the page info bubble entry.
Add WPT testdriver permission request support; test with granted&denied.
Make RenderFrameHostImpl own ScreenEnumerationImpl; adjust bindings.
(supports requesting permission for a given host and its origin)
Limits getScreens() to Window contexts; which seems okay.
Add UX&Privacy-chosen strings + sha hashes for translation screenshots.
Test michaelwasserman.github.io/window-placement-demo with:
chrome://flags#enable-experimental-web-platform-features OR
$ chrome --enable-experimental-web-platform-features
Bug: 994889, 897300
Test: Window Placement setting and permissions work for getScreens().
Change-Id: Iac38133c966d20d9a04c80d999091df16f9fd5c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2173342
Commit-Queue: Michael Wasserman <msw@chromium.org>
Reviewed-by: Kamila Hasanbega <hkamila@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#766929}
--
wpt-commits: 00b32d5054a9b61a451b7b99ae9c064935b770c6
wpt-pr: 23354
Automatic update from web-platform-tests
Fix some path animation WPTs
These tests incorrectly assumed that getAttribute('d') would return the
animated path data (string).
Since there are differences between UAs with how animated path data can
be accessed, add a helper (assert_animated_path_equals) that factors in
these differences, and also allows to compare the result with an
epsilon.
This should make these tests pass in Gecko as well (and probably at
least partially in WebKit).
Bug: 735820
Change-Id: I2d0b0f3b0c34f95dbc75f576567e256231d55a11
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2190632
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#766924}
--
wpt-commits: c07eb06124e4fe32a6269b29b2521dad71189f73
wpt-pr: 23479