Automatic update from web-platform-tests
ScrollAnchoring: Prioritize focus/find-in-page during anchor selection.
This patch updates the scroll anchoring selection to consider
- focused element
- find-in-page active match results
If an anchor is selected out of those candidates, then it is used.
Otherwise, we proceed with the DOM traversal.
This is updated due to changes in the spec:
396d0cf9dc
Fixed: 1066924, 1066982
R=chrishtr@chromium.org, flackr@chromium.org
Change-Id: I1af88dfdeea374c17161b86981b10fbdcecc3a1a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2199603
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#768809}
--
wpt-commits: 3f7e4a75423bb6025be6011e4c86ac53939f4d15
wpt-pr: 23580
Automatic update from web-platform-tests
[COEP] Create reporter for initial empty document
Initial empty documents have a special navigation path, which leads to
missing reports for cross-origin embedder policy violations. Fix the
issue by creating a CrossOriginEmbedderPolicyReporter in the special
navigation path.
Bug: 1052764
Change-Id: I5825eb2946dc00f9e042b55e602fd786dc2d1adc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097800
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#768780}
--
wpt-commits: f597fd3b0f531feeab70f697025bc242361aa444
wpt-pr: 22183
Automatic update from web-platform-tests
Clipboard API Tests: Automate Web Platform Tests
Since https://github.com/web-platform-tests/wpt/pull/20461 and
https://github.com/web-platform-tests/wpt/issues/5671 were fixed, it now
becomes possible to automate some Web Platform Tests, and have them run
on all browsers automatically.
Clipboard API tests previously were duplicated in non-WPT in order to automate
them via PermissionsHelper and detect regressions.
This allows us to shed a lot of duplicate tests, as well as a difficult-to-remember
process of remembering to update both test suites when changes were made.
Bug: 1076691
Change-Id: Ibdfdf37e75da68d7a4b1e2ba986e4198b73230ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2065346
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#764967}
--
wpt-commits: 957c333350503196cc1bf72cc9f6d8b4fdfc2b2c
wpt-pr: 23332
Automatic update from web-platform-tests
[client hints] Match update behavior to the spec.
Accept-CH: from headers, should override, not merge; including having ""
disable things.
In http-equiv, OTOH (where it doesn't persist), it should still merge.
Change-Id: I5c3c94023b10b265e63a8abe29a431bd1da8dadf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2093032
Commit-Queue: Maksim Orlovich <morlovich@chromium.org>
Reviewed-by: Christian Dullweber <dullweber@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#766003}
--
wpt-commits: 90015af47ca0df30dab8f2dde279de5ee46362ca
wpt-pr: 23375
Automatic update from web-platform-tests
[client hints] Enforce the top-frame requirement.
This involves some test updates; of particular note is that
iframe-no-accept-ch.php helper didn't use to test what it thought it
did since it was in the wrong directory.
Change-Id: I70dc9055487b69946548ecc8b2fafb270a508438
Bug: 1078353
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2140918
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Commit-Queue: Maksim Orlovich <morlovich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#766366}
--
wpt-commits: ea0378b06e23f3e68c5d8f90bad36bbe6f7c4c8a
wpt-pr: 23410
Automatic update from web-platform-tests
Fix computed style for outline-offset allowing decimal values
This patch stores outline-offset as a LayoutUnit
and it provides a method ComputedStyle::OutlineOffsetInt()
to use it in the rest of the code without modifications.
BUG=1068107
TEST=external/wpt/css/css-ui/parsing/outline-offset-computed.html
Change-Id: Ice8a425b73fc7ba179411a951d91ac1fef345f00
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2199456
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Manuel Rego <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#768709}
--
wpt-commits: 9fe4d12de6e7ae38533eeb8b7cf8f70193dadf3a
wpt-pr: 23575
Automatic update from web-platform-tests
[css-ruby] test parsing of the ruby-merge property (#23591)
See https://github.com/w3c/csswg-drafts/issues/5004
--
wpt-commits: 48950262c7bfde62ce876471f354b878b06958ce
wpt-pr: 23591
Automatic update from web-platform-tests
[Image-Orientation] Have ImageBitmap.width and .height report oriented sizes
ImageBitmap has only width and height properties, forcing us to choose
one of oriented or unoriented values to report. Given oriented usage is
now the default, we'll change the reported sizes to match the used sizes.
A spec issue will be raised to add naturalWidth or orientedWidth so
that developers can get the data they want.
Also fix a broken path in drawImage-with-src-rect-ref.html
Bug: 1082451
Change-Id: I4dd59766769bbb7175d8216845f19f9122129e16
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2198654
Auto-Submit: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#768689}
--
wpt-commits: e4d5929bc33925323fe31112159cef8772501034
wpt-pr: 23577
Automatic update from web-platform-tests
Reland "De-flaky pointerevents/pointerevent_capture_mouse.html"
Because of Linux memory leak, pointerevent wpt tests
pointerevents/pointerevent_capture_mouse.html is flaky, we
should finish the test in the actions promise's callback to guarantee
the actions are all executed before the test finishes to avoid memory
leak.
Bug: 998948
TBR=nzolghadr@chromium.org,lanwei@chromium.org
Bug: 998948
Change-Id: I01ebc670d85b12e0d9490e0384f358574746ce63
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2200319
Reviewed-by: Lan Wei <lanwei@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#768661}
--
wpt-commits: ae1e2d51f38e208f3d07a97b5d82f9ca0dda2c94
wpt-pr: 23589
Automatic update from web-platform-tests
Reland "De-flaky pointerevents/pointerevent_capture_mouse.html"
Because of Linux memory leak, pointerevent wpt tests
pointerevents/pointerevent_capture_mouse.html is flaky, we
should finish the test in the actions promise's callback to guarantee
the actions are all executed before the test finishes to avoid memory
leak.
Bug: 998948
TBR=nzolghadr@chromium.org,lanwei@chromium.org
Change-Id: Ic7ce443fc32caa2a78aad133d260645bc57e8fbe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2199710
Reviewed-by: Lan Wei <lanwei@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#768638}
--
wpt-commits: 94f54fe0fd00f7c0b4eda08b36becc90ecc28d29
wpt-pr: 23588
Automatic update from web-platform-tests
[FlexNG] Fix hittesting for pseudo-element flex-items.
pseudo-elements are a little different when it comes to hit-testing.
If they get hit, they don't nessecerily add themselves as the resulting
node hit-test. Instead the parent which requested the hit-test will
try and add themselves if no node is present.
We had this logic previously, but only for non-atomically painted
block-level children.
This patch adds this logic for atomically painted block-level children.
Bug: 1081789
Change-Id: I2d013dea0f865c80cedc3ed70ca80f0aea83b308
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2200280
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#768591}
--
wpt-commits: f6023370c4243a9a79fb6a6712a5fa4d1dc522f8
wpt-pr: 23586
Automatic update from web-platform-tests
[AspectRatio] Handle min-inline-size: auto for aspect ratio
For the default min-height/width, aspect-ratio should only be the minimum
size, and the resulting inline size should grow to fit all the content:
https://drafts.csswg.org/css-sizing-4/#aspect-ratio-minimum
This is the inline version of https://crrev.com/c/2186076
Bug: 1045668
Change-Id: I55eb523ef53df09a64f55ea2883abeb75e1d778c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2197341
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Auto-Submit: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#768474}
--
wpt-commits: 47f7c7004aa06e75ab63e9d1dc575a1e5fdf9f1c
wpt-pr: 23556
Automatic update from web-platform-tests
[FlexNG] Clear measure result if layout dirty, and layout result is set.
There was a subtle bug with the measure layout result.
We could get into a state previously where the "measure" layout result,
was invalid (pointing to a previous layout). We'd then hit the cache
using the "measure" slot, causing a UAF.
This patch fixes this issue in two different ways:
1) Clears the measure slot when we are setting a layout result, and we
needed layout.
2) Within ComputeMinMaxSizes use the "measure" cache-slot.
An additional subtle issue was uncovered while investigating this, where
it was possible to hit an incorrect layout result.
Now the "measure" cache-slot should only be used, if it is guaranteed
that a subsequent layout will occur for that node.
Bug: 1081086
Change-Id: I08267eadedc7599075e4b6867d341223999ad9f6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2198716
Reviewed-by: David Grogan <dgrogan@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#768473}
--
wpt-commits: d1207b30692ff86530b3bf1884a0197e9c4c4585
wpt-pr: 23570
Automatic update from web-platform-tests
Fix test time out on feature-propagation-to-auxiliary-context.html
The test is flaky because the number of subtests run depends on how
many features are available in feature policy. This number grows through
out time and eventually causes a timeout occasionally.
The solution is to run a single test that includes all features, instead
of running a subtest per feature.
Bug: 1076410
Change-Id: I9085768d3e000892cef94d661552f4cb518e08ee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2195441
Commit-Queue: Charlie Hu <chenleihu@google.com>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#768370}
--
wpt-commits: 34fb486956c519acc376f8974a1d9aa223436b32
wpt-pr: 23522
Automatic update from web-platform-tests
De-flaky pointerevent_releasepointercapture_invalid_pointerid.html
Because of Linux memory leak, pointerevent wpt tests
pointerevent_releasepointercapture_invalid_pointerid.html is flaky, we
should finish the test in the actions promise's callback to guarantee
the actions are all executed before the test finishes to avoid memory
leak.
Bug: 998948
Change-Id: I4c5166f2e3fae15e5d0bcfda684351486f3f9bd9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2197515
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#768346}
--
wpt-commits: d97cf725efb157a49d5e222b12544c5b3ce43ac1
wpt-pr: 23554
Automatic update from web-platform-tests
De-flaky pointerevents/pointerevent_capture_mouse.html
Because of Linux memory leak, pointerevent wpt tests
pointerevents/pointerevent_capture_mouse.html is flaky, we
should finish the test in the actions promise's callback to guarantee
the actions are all executed before the test finishes to avoid memory
leak.
Bug: 998948
Change-Id: I571dbe328c34f92e6b5f1feb540ede79d5ec0ce3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2197423
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#768342}
--
wpt-commits: 19b4f3481fd481ca71e9b846ded1c21cd0a3c051
wpt-pr: 23557
Automatic update from web-platform-tests
[ResourceTiming] Fix flaky test
Looks like the recent change to status-codes-create-entry.html made it
flaky, so this CL undos that. It also removes the analogous check in the
new test cross-origin-status-codes.html.
TBR=yoavweiss@chromium.org
Bug: 1082046
Change-Id: I8efadeb117905c1e665ef010bca32dd49664b4ec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2198606
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#768273}
--
wpt-commits: fa5c01c9b7f67eeb11e6b32453bec8968c8ceca8
wpt-pr: 23573
Automatic update from web-platform-tests
[wptserve] Clarify response.set_error takes text
This message is eventually JSON encoded and json.dumps only takes text
strings in Python 3.
--
wpt-commits: dc56b06fd1fa4f1e85a191c22294503c166464ab
wpt-pr: 23555
Automatic update from web-platform-tests
Add more file: URL drive letter tests
From https://crbug.com/1078698, plus lowercase variants.
--
wpt-commits: 6d82a3b1c7c79608aa8045666922c79accf917f6
wpt-pr: 23541
Automatic update from web-platform-tests
Dirty font when specifying writing-mode/text-orientation:initial
Only ApplyValue would set the value via StyleResolverState, which is
responsible for the font-dirtying. This CL makes ApplyInitial and
ApplyInherit go through StyleResolverState as well.
Bug: 1081659
Change-Id: I18ac7c54be3da90ac4c97caa242ecfb4fbb3c515
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2199257
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#768259}
--
wpt-commits: 6e0c010743f1e77c8d181df9a1ee85a045e494fb
wpt-pr: 23563
Automatic update from web-platform-tests
Run Taskcluster on draft PRs
Drop the "ready_for_review" condition, since that's for transitioning from draft to normal PR.
--
wpt-commits: 790750052a671417455746921f6f814b576db7fa
wpt-pr: 23566
Automatic update from web-platform-tests
MathML: Regenerate tests for the operator dictionary (#23558)
- Update to the latest dictionary entries.
- Remove accent tests since default is true. https://github.com/mathml-refresh/mathml/issues/151#issuecomment-596040584
- Split into smaller files to reduce timeout risks.
--
wpt-commits: 46fe8740553c7e481dee30ab11165decc49cb100
wpt-pr: 23558
Automatic update from web-platform-tests
Invalidate style for inner editor when focus changes.
The inner editor style invalidation relied on marking the element style
dirty during style recalc if the host input style changed, but that
might not be the case if the author overrides any focus styles.
Bug: 1078663
Change-Id: I2914ff9bebc4bc239ca29ced7365b2c9155ebbb0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2196583
Reviewed-by: Ionel Popescu <iopopesc@microsoft.com>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#768172}
--
wpt-commits: 41769744060adc5877bf51085bfa98b16fce5737
wpt-pr: 23546
Automatic update from web-platform-tests
[ua-ch] Ensure UADataValues' entries are initially undefined
The UA-CH IDL [1] defines UADataValues as initially undefined.
That makes it so that if someone doesn't explicitly ask for a value,
the UADataValue object will not contain it.
This CL aligns the implementation with the spec.
[1] https://wicg.github.io/ua-client-hints/#interface
Bug: 1081837
Change-Id: I4c4abf19537796b2c192c70be0860b004892f734
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2196487
Commit-Queue: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Maksim Orlovich <morlovich@chromium.org>
Reviewed-by: Aaron Tagliaboschi <aarontag@chromium.org>
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#768137}
--
wpt-commits: 3ef4c1f9a6129afc4caf7c9b4acd51a91df196c1
wpt-pr: 23548