Automatic update from web-platform-tests
[css-text] Test other space separators for various values of white-space (#18274)
--
wpt-commits: d2416ea88f7877f31e6b9741d5f79a7421a7eab3
wpt-pr: 18274
Automatic update from web-platform-tests
[css-text] verifying the behavior of line breaking classes for values of white-space other than normal (#18272)
Closes#17997
--
wpt-commits: b67a83472e8264b30946c399edec6f998e5461ce
wpt-pr: 18272
Automatic update from web-platform-tests
[css-text] Make tests independent of any specific font (#18268)
The tests were attempting to use a font that is not present in the repo,
and happened to work because most systems' default font's metric are
close enough. Using monospace and measurements in ch makes this reliable
rather than a happy coincidence.
Closes#17995
--
wpt-commits: 3750472d5f9cb9fbeca82d42b175a703a83959f6
wpt-pr: 18268
Automatic update from web-platform-tests
[css-text] Mark as SHOULD tests for recommended behavior (#18269)
Closes#17996
--
wpt-commits: 369c3db274f75a0d78b8f01ba587eebe2b8a3d09
wpt-pr: 18269
Automatic update from web-platform-tests
Update the expected results of calc() serialization in motion-1. (#18263)
Per the current discussion of
https://github.com/w3c/csswg-drafts/issues/3335,
it'd be better to update the serialization of calc() for [motion-1].
At least for now, Firefox matches this behavior.
--
wpt-commits: 661ea3afb17775fdbc71620e8a695416aec99130
wpt-pr: 18263
Automatic update from web-platform-tests
[docs] Introduce tutorial on writing reftests (#17811)
Tutorials are a proven way of helping potential contributors orient
themselves quickly. By providing concrete instructions that are focused
on one specific task, projects can give readers a sense of the
contribution experience and offer a starting point for learning any
additional details that are relevant to their particular goals.
Replace existing content which demonstrates the contents of a reftest
with a complete narrative describing how and why such a test is
authored.
--
wpt-commits: ddc6346ec78dcf134331193d1e5347abb96407e4
wpt-pr: 17811
Automatic update from web-platform-tests
[wpt] Support detecting Chrome for Android version
Consequently, we can now install the correct ChromeDriver version.
* The change also includes some drive-by whitespace fixes in the file.
--
Allow custom package names for Chrome Android
1. [wptrunner] chrome_android now honours (and requires) the
--package-name flag instead of hardcoding the package name.
2. [wpt] chrome_android now chooses the correct official package name
depending on the channel.
3. [wpt] chrome_android correctly sets browser_version.
4. [wpt] drive-by change: update the logic for adding --binary-arg &
--webdriver-arg in chrome & chrome_android (now they both add
--enable-experimental... to binary_arg and --disable-build-check to
webdriver_arg when running dev or canary channel).
--
wpt-commits: cc864ad313dafdaefa90b483818ed5a603803a41, 2a4e78b2c66b7a6589c50c44dda31e5cf215421f
wpt-pr: 18239
Automatic update from web-platform-tests
Move recently translated tests to WPT
Move tests that can be wp-tests to
the corresponding folder.
The tests should stay exactly the same.
Bug: 985335
Change-Id: I61b76803c935c6dd4cc69241d7de76720eaf668e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730457
Commit-Queue: Edvard Thörnros <edvardt@opera.com>
Auto-Submit: Edvard Thörnros <edvardt@opera.com>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683582}
--
wpt-commits: 2882eb7cdbc18f582ad2145cf5b86529886478c7
wpt-pr: 18234
Automatic update from web-platform-tests
Only clone wpt if web-platform-tests directory is missing
This allows bind mounting the directory from the host
--
Add some wpt commands for interacting with docker
The docker command line is a pain so add some helper commands to
do the most useful things for working in the docker image locally
--
Update tools/docker/frontend.py
Co-Authored-By: Sam Sneddon <me@gsnedders.com>
--
wpt-commits: 8bbad062984896cff6a0d2dadc233fe9f38d3c21, f84735d76f6382065ade94c44c74628ef0adc2a8, 3a0599553f29839f87a9b72316fb72f3ec4c2e66
wpt-pr: 18080
Automatic update from web-platform-tests
The expected height of the green box is wrong (#17174)
* Ref should be 22em and test must grow to achieve the expected height.
* Just changing the ref and test green box height to 19
* Make nbsp; visible if it sticks out
--
wpt-commits: 04c4ecacbeb2c280dd4740f72ad6f3d2846e4753
wpt-pr: 17174
Automatic update from web-platform-tests
Update layout tree rebuild root after removing pseudo element.
We tried to avoid marking the pseudo element when it was about to be
removed, but the pseudo element earlied out before removal if it wasn't
marked for re-attachment causing the element not to be removed.
Notify the StyleEngine about removal instead, so that it can update the
traversal root. For normal elements the StyleEngine is notified through
ChildrenRemoved().
Bug: 989894
Change-Id: Ia2bf52c9bed157c4ac806a10b9367b0f99038974
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1732096
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683543}
--
wpt-commits: 4114304c6526b10034c92d04e769a70e4cbdd443
wpt-pr: 18249
Automatic update from web-platform-tests
MathML: Move tests for vertical math into .tentative.html for now. (#18253)
https://github.com/mathml-refresh/mathml/issues/18
--
wpt-commits: 8da4c04051c2e456398448b9a5b758c666688474
wpt-pr: 18253
Automatic update from web-platform-tests
SVG: marker shorthand is empty string if longhands do not match
The marker shorthand serializes as 'none | <marker-ref>'
https://svgwg.org/svg2-draft/painting.html#MarkerShorthand
If marker-start, marker-mid and marker-end do not all have
the same value, it serializes as the empty string.
Change-Id: I2c3fbcfd308119a7f258a7f269f93f092fabbfaa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724707
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Auto-Submit: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683433}
--
wpt-commits: 851bf68b39b510c262a9a33b76811341746e6a84
wpt-pr: 18167
Automatic update from web-platform-tests
[CSP] Check inline script CSP in prepare-a-script
This CL moves the inline script CSP check from
PendingScript::ExecuteScriptBlock() (#execute-the-script-block)
to ScriptLoader::PrepareScript() (#prepare-a-script)
as spec'ed.
This CL removes Script::InlineSourceTextForCSP()
which is no longer used.
Behavior changes (the new behavior is spec-conformant and thus
this CL adds WPT tests):
- Previously <script>'s error events were fired
when inline script CSP check fails,
while after this CL the events are no longer fired.
Test: scripthash-basic-blocked-error-event.html
(Moved from layout test with expectation changes)
This CL makes Chromium's behavior align with Firefox and Safari.
- If the nonce attribute is changed or the CSP list is updated
after prepare-a-script before evaluation,
previously the new nonce/CSP were used for CSP,
while after this CL the old nonce/CSP
(at the time of prepare-a-script) is used.
Test: scriptnonce-changed-*.html
This CL makes Chromium's behavior align with Firefox.
(Safari's behavior is different from any other browsers)
This CL also adds scripthash-changed-*.html (just for symmetry
with scriptnonce-changed.html), which pass only on Chromium.
Bug: 964537
Change-Id: I8673956101d9d13708c452db23258f125cb3d256
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1618262
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683391}
--
wpt-commits: 79d560495d9f5c996ef103a892b479baaa1b2df0
wpt-pr: 17583
Automatic update from web-platform-tests
[WPT/common/security-features] Use "unset" instead of "None" in filenames
`delivery_value` can be None.
Generated files will be updated after some more changes, not now.
Bug: 906850
Change-Id: Ia40b1cb4a75d14384092fb1fb84c51df8411ef15
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1723012
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683393}
--
wpt-commits: eb37e2b0b26e8be15b2c719b810cb66b1e608dc2
wpt-pr: 18244
Automatic update from web-platform-tests
[WPT/common/security-features] Support multiple policy deliveries in top-level Documents
Currently, policy deliveries (and thus <meta>, HTTP headers) in top-level Documents
are processed by `handleDelivery()` methods, which accept only one policy delivery.
This CL
- Merges `handleDelivery()` methods into a single `handle_delivery()`,
- Introduce `util.PolicyDelivery` to represent policy deliveries as
explicitly typed objects, and
- Extends `handle_delivery()` to accept multiple policy deliveries.
Bug: 906850
Change-Id: Iadbef1240c4855967e40f81cb3417389cff5c9eb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1723229
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683355}
--
wpt-commits: 88fcfe65bbdd13215452d8d2bc57d0c0336fde17
wpt-pr: 18126
Automatic update from web-platform-tests
Introduce automation to support pull rqst previews (#17680)
* Introduce automation to support pull rqst previews
Today, http://w3c-test.org automatically fetches and publishes the code
from "preview-enabled" pull requests to WPT. It defines eligible pull
requests as those authored by project collaborators and those where a
collaborator has left a special GitHub comment. That mechanism has a
number of drawbacks:
- The configuration is hidden. Only those with admin rights can review
the GitHub webhook upon which the solution relies.
- Pull request state is opaque. It's not possible to know when/if a pull
request has been recognized by w3c-test.org from the pull request or
from WPT (though this information is available at the undocumented
page http://w3c-test.org/submissions/).
- Server state (i.e. the collection of which pull requests are
considered "active") is likewise opaque. Also, in the absence of a
backup mechanism, it is non-recoverable following a system crash
- Previews cannot be disabled
This patch is one component of an attempt to reimplement this service in
a way that gives more control to the WPT administration and stores more
state in the WPT repository.
- Maintains state via git tags. This avoids the complexities of an
external storage system (access credentials, back up policies, etc.)
- Observes eligibility using GitHub pull request labels. This makes the
state of the system apparent from the pull requests themselves. It
also provides a more ergonomic and discoverable mechanism for
enabling/disabling previews
This is facilitated by a script that is executed as a GitHub Action.
Although the script relies on a secret access token, it is *not* limited
to use for pull requests from trusted collaborators due to the way
GitHub Actions are executed [1]
> ### Pull request events for forked repositories
>
> [...]
>
> #### Pull request with base and head branches in different repositories
>
> The base repository receives a `pull_request event` where the SHA is
> the latest commit of base branch and ref is the base branch.
With this in place, a far simpler "preview" server can be built. The
simplified version will need no privileged information; it will only
need to poll the git repository for tags and synchronize its deployment
according to the result.
[1] https://developer.github.com/actions/managing-workflows/workflow-configuration-options/#pull-request-events-for-forked-repositories
* fixup! Introduce automation to support pull rqst previews
Add support for Python 3
* fixup! Introduce automation to support pull rqst previews
* fixup! Introduce automation to support pull rqst previews
Use generic git refs instead of tags
* fixup! Introduce automation to support pull rqst previews
* fixup! Introduce automation to support pull rqst previews
React to events from closed pull requests
* fixup! Introduce automation to support pull rqst previews
--
wpt-commits: 89f8327545d8d34f200da06bd22fc16da44c246f
wpt-pr: 17680
Automatic update from web-platform-tests
Update chromium log formatter to treat subtest fails as test failure. (#17944)
* Update chromium log formatter to handle subtest fails as test failure.
If a test has subtest failures the runner reports the test status as a
success, but for Chromium this is generally considered a failure. So we
keep track of which tests have subtest failures and flip their status to
FAIL if necessary.
--
wpt-commits: 8faf1fb3d5cfe08ed15eb2acd8aa1460edf1c3ee
wpt-pr: 17944
Automatic update from web-platform-tests
[wptrunner] Release actions before closing windows
Make sure all inputs are released and states are cleared before starting
a new test.
This change deflakes some pointerevent tests on Chrome. e.g.
/pointerevents/pointerlock/pointerevent_pointermove_in_pointerlock.html
is now crashing *consistently* with "invalid argument", and
/pointerevents/pointerevent_touch-action-keyboard.html
no longer crashes with "invalid input state".
--
wpt-commits: 1cb5f2830ac1d2a1a6fcf08e330e588d387b2731
wpt-pr: 17864
Automatic update from web-platform-tests
Use To<Dynamic> for rebuild root to make sure we don't crash.
We were able to SetNeedsReattachLayoutTree() on a Text node where none
of the ancestor elements had a LayoutObject and the Document had a <br>
as a documentElement. The reason is that LayoutView does not allow a
LayoutBr child which meant we recomputed styles for the whole subtree,
but no LayoutObjects were created. Setting the text data on the text
node would mark it for re-attachment (in case it didn't have a
LayoutText because it used to be a non-rendered white-space). If it was
in a display:none subtree we wouldn't have reached the text node during
recalc, but because of LayoutView rejecting the LayoutBr, we already had
ComputedStyle all the way.
Bug: 989827
Change-Id: I72ae371466e607baf4caffad9ed634beb2a66bf5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731112
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683135}
--
wpt-commits: ec90c902eeb0612dbce30047ff51414c8b26d603
wpt-pr: 18232
Automatic update from web-platform-tests
Move ChromeAndroid to ExecutorWebDriver (#18186)
Fixes#16056
Docs changes:
* Remove instructions for special setups that are no longer needed.
* Document more existing limitations of the implementation.
--
wpt-commits: ab508a6ecf41df2acec4c09d2b516a550ce41fe9
wpt-pr: 18186
Automatic update from web-platform-tests
Update the expected test metadata format to incude known intermittent statuses
Currently, the `expected` field in the test metadata accepts only one status. This patch adds
the ability to include known intermittent statuses in this metadata.
The existing metadata format is:
```
[test]
[subtest]
expected: PASS
```
This new format, if there is a known intermittent status to record, will be:
```
[test]
[subtest]
expected: [PASS, FAIL]
```
The first status will always be the "expected" status. The following statuses in the list are
"known intermittent" statuses. The statuses are ordered based on `tree.result_values` counts
during `build_tree()`.
Tests have been added to test_update.py to account for the following circumstances:
- an existing metadata file with only one expecte status needs updating with a known intermittent
- a file with an existing known intermittent needs to be updated with an additional status
- an intermittent status is now the expected status, and the expected status is now intermittent
- a new metadata file needs to be created with a known intermittent status
testrunner.py has been updated to exclude tests with a `known_intermittent` status from the
`unexpected_count`.
A test has been added to test_expectedtree.py to ensure the `tree.result_values` is counting
correctly.
Differential Revision: https://phabricator.services.mozilla.com/D37729
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1558954
gecko-commit: fbc5881fd4b6c2d758ba46faf21e045e500f7676
gecko-integration-branch: central
gecko-reviewers: jgraham
--
Remove trailing whitespace
--
Mark all tests as failing on Python 3
--
wpt-commits: 0a82a1b98b191b6ccda29145a55610058f247526, 44c4bb1c694ce507923e5e1ca39534fbdce823d2, e1498d56d927641355db6cd09492489b0a918fc6
wpt-pr: 18230
Automatic update from web-platform-tests
Add stronger test for MathML in SVG foreignObject element. (#18227)
Existing tests only check whether a foreinObject with
requiredExtensions="http://www.w3.org/1998/Math/MathML" is displayed or
selected inside a switch. This commit adds a more advanced test that actually
verifies that some basic math layout happens.
--
wpt-commits: 5cc6d2d3262c32277c68d45993289660162693c3
wpt-pr: 18227
Automatic update from web-platform-tests
Give more content to foreign-container (#18209)
Chromium has behavior different from Firefox. For an empty span in
a div with padding the empty span is positioned at (0, 0). The same
effect is seen for MathML, so add some text content to force
an inline flow.
--
wpt-commits: dbf688e8d16b4483de532ceb29f7de12be12573e
wpt-pr: 18209
Automatic update from web-platform-tests
MathML displaystyle: Test display="inline" and attribute value cases. (#18220)
* MathML displaystyle: Test display="inline" and attribute value cases.
This introduces a new helper function to easily apply transforms to attribute
values and uses it to test different string cases for the displaystyle and
display attribute values. This also add new tests for a math with explicit
display="inline" and a displaystyle attribute and check case-insensitivity
of the display attribute in relations/html5-tree/display-1.html
--
wpt-commits: f63482b40c3a8964913e18b69e9223da65a37be0
wpt-pr: 18220
