Automatic update from web-platform-tests
[webnfc] Introduce IDLs for NFCErrorEvent and NFCErrorEventInit.
This CL introduces IDLs for NFCErrorEvent and NFCErrorEventInit
interfaces, and updates the baseline of relevant wpt tests.
http://w3c.github.io/web-nfc/#dom-nfcerrorevent
The corresponding spec changes were introduced in
https://github.com/w3c/web-nfc/pull/184
BUG=520391
Change-Id: Ia8af8b49f53be7161b7e7b0f4e45f617c4991473
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1652968
Commit-Queue: Leon Han <leon.han@intel.com>
Reviewed-by: Leon Han <leon.han@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669482}
--
wpt-commits: 4100d1d51b885185c50902397f7d203d89efc24c
wpt-pr: 17263
Automatic update from web-platform-tests
[Azure Pipelines] avoid parenthesis in job names
The Azure Pipelines integration with GitHub Checks produces checks on
the form "$pipelineName ($jobName)", leading to check names like
"Azure Pipelines (tools/wptrunner/ unittests (macOS))". Use colons as
separator instead, like the existing "wpt.fyi hook" jobs.
Also change some step names for consistency.
--
wpt-commits: e75855649360298870a40ed78874bd4ab1470c20
wpt-pr: 17265
Automatic update from web-platform-tests
Add more direction tests (#17345)
* Add more direction tests
Put these in a new directory.
* Make direction.html use testharness.js
--
wpt-commits: fdf8ff01960e031fe0381133f5a39e1b8e372454
wpt-pr: 17345
Automatic update from web-platform-tests
[trusted types] Check text node insertions into <script> elements.
insertAdjacentText into <script> elements can be used to bypass
Trusted Types checks. This change fixed that hole by adding TT checks
to related Node API methods, and changing insertAdjacentText to use
the public methods.
See additional discussion on the root issue in
https://github.com/WICG/trusted-types/issues/133
Bug: 739170
Change-Id: Ie26b2aca2d60c7e14a0118c6fd957f32928afabf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1547746
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669210}
--
wpt-commits: 90a794e8e93a5e22e7cb3b2f8c79d751989fa7b0
wpt-pr: 17230
Automatic update from web-platform-tests
MSE: Let external/wpt/.../mediasource-play have longer timeout
This test normally takes only 1-2 seconds to execute on Chromium Mac
release builders, but can timeout at low frequency (3 times in > 100
builds). Per WPT documentation [1], this change marks the test timeout
as "long". In Blink, this change also removes the flaky timeout test
expectation for this test.
[1]
https://web-platform-tests.org/writing-tests/testharness-api.html#harness-timeout
BUG=971252
TEST=confirmed locally with Blink's web test runner and injected test
delays that this change allows the test to run over 6 seconds without
failing with timeout.
Change-Id: Icf60260640f201f3fc3c072c6bef9097bff928df
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1659132
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669043}
--
wpt-commits: 11147d0843d3282784dfc93a5bdc0882311f52f2
wpt-pr: 17322
Automatic update from web-platform-tests
Fix the case where an element contains both filter and backdrop-filter
Previous to this CL, if an element was styled with both filter and
backdrop-filter, the filter effect was not properly applied to the
filtered backdrop contents, because a separate filter property node
gets created for the filter, and the backdrop-filter effect node
does not contain the filters. With this CL, paint_layer appends
the filters to the backdrop-filters list, so that Viz has access
to those.
Bug: 973907
Change-Id: I255b73433d75e0551d817134fa50d5e0e35b87df
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1658654
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669006}
--
wpt-commits: 9bb8217b7e6e5a2174522159bebc42fe4e401107
wpt-pr: 17316
Automatic update from web-platform-tests
Disallow symlinks (#17315)
* Lint to ensure there are no symlinks in the tree.
Would be good to disallow whitelisting this one somehow, but that's a
larger change.
* Remove symlink
* Update tools/lint/lint.py
Co-Authored-By: Robert Ma <bob1211@gmail.com>
* Update tools/lint/tests/test_path_lints.py
--
wpt-commits: 8d6992deac82fe032594b6a8cfa2e33723c8812a
wpt-pr: 17315
Automatic update from web-platform-tests
Remove expansion of backdrop-filter input for pixel-moving filters
See [1] for the PR for the spec change. Essentially, with this CL,
the input to the filter will be the bounding box of the element
with backdrop-filter. The bounds will not be expanded for pixel-
moving filters, and will not include extra border for children.
Note that the rebaselined layout tests are all for very small
single-pixel errors, except for backdrop_filter_blur_outsets.png
and backdrop-filter-boundary-expected.png, which change because
of this new behavior.
This needs a (small) spec change, but it will be beneficial in
these four ways:
- It agrees more closely with existing Safari behavior.
- It improves performance, by filtering fewer pixels in the
case of pixel-moving filters.
- Developers have been disappointed with the existing behavior
of bringing in pixels from outside the bounds of the
element, and have requested a way to turn this behavior off.
See the discussion starting at [2].
- It eliminates the problem of crbug.com/972173, where content
outside the renderer viewport can get dragged into the filter.
[1] https://github.com/w3c/fxtf-drafts/pull/342
[2] https://bugs.chromium.org/p/chromium/issues/detail?id=497522#c196
Bug: 972173,497522
Change-Id: I18cc6d08cf9fde263b9e166b5e96ea57a1c41973
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1650418
Reviewed-by: enne <enne@chromium.org>
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#668894}
--
wpt-commits: b90e70c4557b94ca735e6c8b20958c77ef02306e
wpt-pr: 17310
Automatic update from web-platform-tests
Remove relations/css-styling/lengths-2 (#17309)
This tests namedspaces, which were removed from the Core spec:
https://github.com/mathml-refresh/mathml/issues/75
--
wpt-commits: 8b26ee28f1e20c1cfbd9b95ddf040f725f747b52
wpt-pr: 17309
Automatic update from web-platform-tests
[LayoutNG] the real youtube button fix
Previous fix worked by eliminating cacheing of OOF Legacy
positioned elements. It was not the right fix.
https://chromium-review.googlesource.com/c/chromium/src/+/1649086
This fix backs out the original fix, and implements the correct fix:
OOF objects positioned by RunLegacyLayout could end up
with a cached layout result that had an old constraint space.
Fix is to force re-cache with new constraint space.
Bug: 970171
Change-Id: Ia9a7faea929083566f406db371ddcef058f2e4ab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1652653
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#668709}
--
wpt-commits: b8eea2d704ec32a88a3b8b46a2d01e96b3a470b5
wpt-pr: 17303
Automatic update from web-platform-tests
Prevent the error from triggering a page error in Worker-nested-importScripts-error
Fixes#23511
--
wpt-commits: 51f5cebccd000d8a021d6d3810e2fa1a8e2e212d
wpt-pr: 17272
Automatic update from web-platform-tests
[LayoutNG] Fix float + nbsp to create a break opportunity
Floats should create break opportunities, and
|NGLineBreaker::Rewind()| assumes this. However, |nbsp|
after floats suppressed the break opportunity, which caused
NGLineBreaker to loop infinitely under certain conditions.
This patch fixes floats to allow break after them.
Note the new behavior is the same as Gecko.
Bug: 972421
Change-Id: Ie8c1d7927c5c282078a20f90941398149ea702a3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1653171
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#668681}
--
wpt-commits: 0b4f8505547ddc457e89df8b898ad445281fb204
wpt-pr: 17281
Automatic update from web-platform-tests
Prevent fooling PerformanceObserver.supportedEntryTypes (#17242)
* Prevent fooling PerformanceObserver.supportedEntryTypes
* Split between any and window
* Long task is only on Window
* CRLF -> LF
--
wpt-commits: 2d2b6ee35d5f4c82c2f698fdb50c49583e8c7f70
wpt-pr: 17242
Automatic update from web-platform-tests
Allow browsers to block mixed content requests from cross-origin tests. (#17300)
Gecko and Blink by default block mixed content requests.
As a result, header-referrer-strict-origin-when-cross-origin.https.html, header-referrer-strict-origin.https.html,
and beacon/headers/header-referrer-unsafe-url.https.html fail in those two browser engines.
Allow the mixed content beacon requests to be blocked in these tests as allowed by the specification:
https://www.w3.org/TR/mixed-content/#should-block-fetchhttps://www.w3.org/TR/mixed-content/#requirements-user-controls
Also fixed a bug in header-referrer-strict-origin-when-cross-origin.https.html that it was not testing cross-origin.
--
wpt-commits: eb12be23e4b86154ea3822fa8d048f4cce43ab55
wpt-pr: 17300
The arrows to jump to the next file aren't sticky but they wouldn't have been visible before this patch so I still think it's an incremental improvement.
Differential Revision: https://phabricator.services.mozilla.com/D39121
--HG--
extra : moz-landing-system : lando