Automatic update from web-platform-tests
Don't look for property containers with multiple fragments.
The MapToVisualRectInAncestorSpace fast-path needs a LayoutObject
with LocalBorderBoxProperties set, so that it can call into
GeometryMapper. If the start LayoutObject does not have one,
it proceeds up the containing block chain until it finds one, and
uses the FirstFragment() of the resulting LayoutObject. This is
wrong in cases where there multiple fragments on the LayoutObject,
because we don't know which one to choose. In such cases, fall back
to the slow path.
Bug: 999551
Change-Id: I887c15c3acbe41432b2ca64e5a1551f3765a5043
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1892058
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#711263}
--
wpt-commits: af0a7431ab977b1c169075a10fd44944b05079f9
wpt-pr: 20013
Differential Revision: https://phabricator.services.mozilla.com/D53587
Automatic update from web-platform-tests
[css-pseudo] Restrict the properties allowed in ::marker
Only the following properties apply to a ::marker pseudo-element:
- all font properties
- `color`
- `text-combine-upright`, `unicode-bidi`, and `direction`
- `content`
Spec: https://drafts.csswg.org/css-pseudo-4/#marker-pseudo
BUG=457718
TEST=external/wpt/css/css-pseudo/parsing/marker-supported-properties.html
The test has 2 failures because font-synthesis and font-variant-position
have not been implemented yet.
Change-Id: I9f82e13bdd14a06a84ee55e352cd5a2c64d6fb97
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1891310
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Cr-Commit-Position: refs/heads/master@{#710995}
--
wpt-commits: bdd57938c6385091bb4120cb7bfb0749ee62b2a1
wpt-pr: 20003
Differential Revision: https://phabricator.services.mozilla.com/D53584
Automatic update from web-platform-tests
Remove Ahem from system setup documentation (#20015)
It is no longer necessary to do anything about Ahem.
--
wpt-commits: 1020f3d916d99e5982cbf55baef9f405ab6e720b
wpt-pr: 20015
Differential Revision: https://phabricator.services.mozilla.com/D53583
Automatic update from web-platform-tests
[Taskcluster] unpin Chrome Dev version (#19999)
* [Taskcluster] unpin Chrome Dev version
Was pinned to 78.0.3904.17 in #19360.
Fixes#19367
--
wpt-commits: 4c7312cffa556b614f9448f0e309f7d8c7d78734
wpt-pr: 19999
Differential Revision: https://phabricator.services.mozilla.com/D53582
Automatic update from web-platform-tests
[webnfc] Separate 'absolute-url' record type from 'url'
This CL introduces a new record type 'absolute-url' based on the spec
change: https://github.com/w3c/web-nfc/pull/373
Now we read/write records containing urls like:
'absolute-url' --> TNF_ABSOLUTE_URI
'url' --> TNF_WELL_KNOWN and RTD_URI
BUG=520391
Change-Id: I7b7a57c613eb1581efa01fd148c6083b26cd078a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1881786
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Reviewed-by: François Beaufort <beaufort.francois@gmail.com>
Commit-Queue: Leon Han <leon.han@intel.com>
Cr-Commit-Position: refs/heads/master@{#711174}
--
wpt-commits: 0abb411331f86f472103183c7ec1136ea21a7e1b
wpt-pr: 19941
Differential Revision: https://phabricator.services.mozilla.com/D53580
Automatic update from web-platform-tests
Use a transformed bounding box when hit testing transformed elements
Hit testing uses a 1x1 rect (i.e., "bounding box" )at the hit test
location to test intersection with boxes in the tree. The current
implementation always uses a 1x1 bounding box in the local coordinate
space of the box being tested, which is incorrect -- for example, if the
box is scaled by 100x, then using a 1x1 bounding box in the local space
is equivalent to using a 100x100 bounding box in the viewport, and as a
result we hit the transformed box even if the hit test location is still
100px away from it.
This patch fixes the issue by also transforming the bounding box, so
that it is always equivalent to a 1x1 rect in the viewport.
Bug: 1015801
Change-Id: Ia23e33d2d14bc51fcb2d4b0953ed48bc5738e20e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1891110
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#711072}
--
wpt-commits: 2e85f94ff9f318dcd7b7b00316f31f79c4151a37
wpt-pr: 20004
Differential Revision: https://phabricator.services.mozilla.com/D53575
Automatic update from web-platform-tests
CSS: Update min-width and min-height parsing WPTs
min-width and min-height were previously defined in
https://drafts.csswg.org/css-box-3/
They supported 'fit-content' as a keyword, not as a function.
`[ [<length> | <percentage>] && [border-box | content-box]? ] | available | min-content | max-content | fit-content`
Now min-width and min-height are exclusively defined in
https://drafts.csswg.org/css-sizing-3/
They support fit-width as a function, not as a keyword.
`auto | <length-percentage> | min-content | max-content | fit-content(<length-percentage>)`
Bug: 856648
Change-Id: I04230a5a530b1455fbd17bbf0aceeabacdd188d4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1885860
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#711067}
--
wpt-commits: f2b9fd8d016b3c06806b2eb6065ff4b1d73cf2c0
wpt-pr: 19968
Differential Revision: https://phabricator.services.mozilla.com/D53574
Automatic update from web-platform-tests
[infrastructure] Refactor tests & extend coverage (#19916)
testharness.js was recently extended with an API to explicitly opt-in to
the "single page test" feature [1]. As per WPT RFC 28 [2], tests which
do not use this API and which do not declare any subtests will soon be
reported as a harness error.
Update some tests which previously opted in implicitly to use the new
API. Update others to instead declare a single subtest (so that they are
no longer single-page tests). Add new tests to fully cover the
conditions under which an uncaught exception or unhandled rejection
could occur.
[1] https://github.com/web-platform-tests/wpt/pull/19449
[2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
--
wpt-commits: b00f6989a451cd003d04463a82918973fcd3fa53
wpt-pr: 19916
Differential Revision: https://phabricator.services.mozilla.com/D53571
Automatic update from web-platform-tests
Revert "[wptrunner] Explicitly ignore certificate errors for Chrome"
This reverts commit 98fe3d29b673c33e468e5661709a4e3ca33189d1.
This only works for the current browsing context controlled by
ChromeDriver, and does not work for service workers.
--
[wptrunner/Chrome] Switch to --ignore-certificate-error
--ignore-certificate-error is a global flag that works for all browsing
contexts including workers.
https://github.com/web-platform-tests/wpt/pull/19999#issuecomment-548115986
--
wpt-commits: 5aad52b1f053f76d4cc5bca3c63dc7a2f454cc20, c9064ef7751ca8b1598d09a32e58c5c53559b01a
wpt-pr: 20006
Differential Revision: https://phabricator.services.mozilla.com/D53570
Automatic update from web-platform-tests
[infra] update the epochs_update cronjob command (#19984)
This patch complements the work initiated in the PR #19873 adding the
still missing epochs branches to the cronjob executed by the Github
Actions.
--
wpt-commits: e87223b25324b92f1312ef1417d0b1259a5f5607
wpt-pr: 19984
Differential Revision: https://phabricator.services.mozilla.com/D53568
Automatic update from web-platform-tests
[WPT/common/security-features] Merge test_case_name
This CL moves `test_case_name` and `test_js` into test HTML templates,
- To merge code from indiviual projects into common/, and
- To prepare for merging multiple scenarios into a single HTML file.
This CL keeps generated test files unchanged.
Bug: 906850
Change-Id: Iad2dd874492b8824f4c97d76a78b09bf8e2ab94f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1889476
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710975}
--
wpt-commits: 1b09f4cc8d7f6a5a6e4492559daaa7780819d39f
wpt-pr: 19989
Differential Revision: https://phabricator.services.mozilla.com/D53567
Automatic update from web-platform-tests
Add unitest for get_epoch_revisions in revlist tool (#19977)
This patch adds unit tests for the `list_tagged_revisons (epoch,
max_count)` function in the revlist WPT tool which is renamed
now to `get_epoch_revisions()` for the sake of clarity.
The goal of adding these tests is to prevent future regressions due
to eventual changes done in this part of the code.
This patch also provides slight modifications in the
`get_epoch_revisions (epoch, max_count)` function replacing the
`print` method invocation with `yield`.
Finally, the patch moves out the `epoch_until` variable in the
function `get_epoch_revisions`, which is defined as an parameter
and also renamed as `until` now.
Related to: Add rev-list wpt subcommad (#19536)
--
wpt-commits: fb4bb83e0a6256d94cc6706a703b5d250a96974e
wpt-pr: 19977
Differential Revision: https://phabricator.services.mozilla.com/D53566
Automatic update from web-platform-tests
[ElementTiming] Add simple test for multi-redirect
Add a redirect chain similar to that being used for ResourceTiming. More
images along with TAO will be added in a followup.
Bug: 1003943
Change-Id: I07a98e6f3b574a1241f33aed60a6bb71e0240a95
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1880539
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710837}
--
wpt-commits: 1429202e7c98f7a20b9afbb957e3ac57da281239
wpt-pr: 19901
Differential Revision: https://phabricator.services.mozilla.com/D53563
Automatic update from web-platform-tests
[fetch] Refactor tests (#19919)
testharness.js was recently extended with an API to explicitly opt-in to
the "single page test" feature [1]. As per WPT RFC 28 [2], tests which
do not use this API and which do not declare any subtests will soon be
reported as a harness error.
Update some tests which previously opted in implicitly to use the new
API. Update others to instead declare a single subtest (so that they are
no longer single-page tests).
[1] https://github.com/web-platform-tests/wpt/pull/19449
[2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
--
wpt-commits: ef85c0ffb5ef120a3165d0f1763e6fa864eb274f
wpt-pr: 19919
Differential Revision: https://phabricator.services.mozilla.com/D53561
Automatic update from web-platform-tests
[WebNFC] Support writing NDEFRecord attributes "encoding" and "lang".
This CL adds support for writing the new NDEFRecord encoding and lang
attributes as specified in https://github.com/w3c/web-nfc/pull/381
It also makes sure ArrayBuffer and ArrayBufferView are valid types for
NDEFRecord data when used in a text record.
Bug: 520391
Change-Id: Ic159ee77eae5d2bcf20857bf533e41cef80db5cb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876390
Commit-Queue: François Beaufort <beaufort.francois@gmail.com>
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Cr-Commit-Position: refs/heads/master@{#710823}
--
wpt-commits: 55b30cad64e25104acb82331d8def75cb4f0c665
wpt-pr: 19885
Differential Revision: https://phabricator.services.mozilla.com/D53559
Automatic update from web-platform-tests
[Trusted Types] Remove modifying eval() callback.
This temporary change disables eval(TT), so all related WPTs are disabled as well. It is necessary to change the v8 callback signature and support throwing exceptions when CSP blocks execution.
Bug: 940927
Change-Id: I9b16f9e9611034111859683eb6b6a31d958fe6eb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872221
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org>
Commit-Queue: Stefano Sanfilippo <ssanfilippo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710803}
--
wpt-commits: 170863d3b49760851da02c1f0c6a1eaec948cd0a
wpt-pr: 19827
Differential Revision: https://phabricator.services.mozilla.com/D53558
Automatic update from web-platform-tests
Support IPv6 literals in KURL::SetHostAndPort
KURL::SetHostAndPort would corrupt IPv6 literals because they contain
":" characters. Make it check for "[]" characters and use the first ":"
after an IPv6 address as the start of the port number if one is present.
Fixed: 1012416
Change-Id: If07a671b48c8c1b24b16883fb9072a86b0de7ebc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871449
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710668}
--
wpt-commits: 5e2d3b33d4dc2d9221446c32c2fd6a3d79768406
wpt-pr: 19858
Differential Revision: https://phabricator.services.mozilla.com/D53553
Automatic update from web-platform-tests
Remove inDocument check for emitting change events
The html spec does not seem to say anything against emitting change
events for input elements which are detached from the DOM. It does say
that immutable input elements should not have change events emitted for
them, but I don't think that having it detached from the DOM means that
it is immutable, especially since we can successfully change the
.checked value while detached from the dom.
Bug: 773680
Change-Id: Ie579ed1f3c34fc03f74554a5685f40c510805f2a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1885093
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710642}
--
wpt-commits: f2f0130e56d6893099b8e0c51fc82bc2ab4b1ce2
wpt-pr: 19960
Differential Revision: https://phabricator.services.mozilla.com/D53552
Automatic update from web-platform-tests
Prevent sandboxed iframe Document from sharing execution context with initial about:blank Document
This change fixes an issue where a sandboxed iframe can be created such
that it contains a sandboxed Document with an opaque origin that still
shares a script context with the iframe's initial un-sandboxed
about:blank Document. The scenario is set up in the following manner:
1) Create a new iframe dynamically, and set its src to a same-domain page
that we are going to sandbox.
2) Insert the iframe into a Document, and synchronously grab a reference
to its initial about:blank Document.
3) Synchronously set iframe.sandbox = "allow-scripts" (this is still
before the same-domain page has loaded in the frame).
4) The iframe’s navigation to the same-domain page occurs, asynchronously.
FrameLoader::ShouldReuseDefaultView is called to determine the mode in
which to load the new page. FrameLoader::ShouldReuseDefaultView fails
to check the iframe’s sandbox flags (it only looks at the CSP ones),
so the navigation proceeds without resetting the type system of the
iframe. The result is that the newly loaded page shares the type
system of the initial about:blank Document.
5) Code in the sandboxed iframe is now free to make changes to its type
system that can affect any usage of the about:blank Document since
they share the same type system. This is a sandbox escape in that if
the same-domain page that the iframe is navigated to contains
user-generated code, it could run outside the iframe. It can also
result in crashes if we poke things in the right way, since an object
that should be considered cross-origin can bleed into the top-level
page, with the result that access checks which are never expected to
fail can now fail.
This change fixes the issue by making FrameLoader::ShouldReuseDefaultView()
check the iframe's sandbox flags via FrameLoader::EffectiveSandboxFlags(),
in addition to the existing check for CSP sandbox flags.
Bug: 1017441
Change-Id: Ide1b13e16b0e0428a243ff47b6e17ae25ad0ff0d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1881315
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Nate Chapin <japhet@chromium.org>
Commit-Queue: Dan Clark <daniec@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#710629}
--
wpt-commits: 1da988941a8c83f13aa71447a188335f5cc35ab0
wpt-pr: 19900
Differential Revision: https://phabricator.services.mozilla.com/D53550
Automatic update from web-platform-tests
[css-text] Use always the BreakIterator to compute the intrinsic size
As part of the preferred width computation of LayoutText objects, we
have an specific function to implement the min-word-fragment of a text.
We are handling the case of break-all and break-word differently, and
that's right. However, we are using the BreakIterator only in case of
break-all. This caused that we consider valid to break grapheme clusters
when computing the min-content size, which leads to wrong values in some
cases, like the one described in the bug.
This CL changes the mentioned logic to rely always into the
BreakIterator, which knows better when is valid to break the text.
Bug: 1013775
Change-Id: Ia152d346a61b6b54eaac185a399b0d572e3aba4d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1857319
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710594}
--
wpt-commits: ae12c777133af976a4ba1d66b138d0fa3cee24d3
wpt-pr: 19808
Differential Revision: https://phabricator.services.mozilla.com/D53549
Automatic update from web-platform-tests
[LayoutNG] Fix not to break after leading out-of-flow objects
r694888 (crrev.com/c/1792467) gave a break opportunity after
OOF objects.
For leading OOF objects, there should not be a break
opportunity, but the patch gave to them too. This patch fixes
not to add a break opportunity if there were no preceding
in-flow objects.
Bug: 1018748
Change-Id: I89a8614cdfd85bed1bb8c2f3b6db892697f7add7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1886130
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710527}
--
wpt-commits: 6a912ffd3db259b1d6a133f589aa30c97f7738e4
wpt-pr: 19970
Differential Revision: https://phabricator.services.mozilla.com/D53548
Automatic update from web-platform-tests
[css-lists] Skip bidi controls when painting symbol markers
Symbol markers are painted as geometric shapes, not as text. However,
they are still represented by a text run, which may break into multiple
fragments. To avoid painting the symbol multiple times, the symbol is
painted only for the first one.
Before this patch, this was simply done by checking that the 'from' data
of the NGTextFragmentPaintInfo was 0.
However, markers can have a non-normal unicode-bidi, because the value
is inherited from the list item, or via the ::marker pseudo-element once
it gets implemented. The problem is that some unicode-bidi values can
insert bidi control characters like U+202A, U+202D, U+2066 or U+2068.
This makes the first 'from' data to be greater than zero, so the symbol
was not painted.
This patch checks whether the first 'from' characters are bidi controls,
if so, the symbol is painted. Otherwise it's not painted.
BUG=1018696
TEST=external/wpt/css/css-lists/list-marker-symbol-bidi.html
Change-Id: If5ec4eee624f27ab63df81940f1fc2ea727a5681
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1884291
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710493}
--
wpt-commits: 971bd53b84e2f7103052265afc540c54faef69ae
wpt-pr: 19956
Differential Revision: https://phabricator.services.mozilla.com/D53546
Automatic update from web-platform-tests
[AnimationWorklet] De-flake stateful-animator tests
Some tests relied on time equality which could be flaky because
internally the time value is converted to base::TimeTicks.
Bug: 1014810
Change-Id: I9530f087c1273907af653f0d81f75569572d2e43
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1886293
Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710443}
--
wpt-commits: aa409fcfc73c881e463fed5101b1c3c1080b8337
wpt-pr: 19982
Differential Revision: https://phabricator.services.mozilla.com/D53545
Automatic update from web-platform-tests
[html] Refactor tests (#19918)
testharness.js was recently extended with an API to explicitly opt-in to
the "single page test" feature [1]. As per WPT RFC 28 [2], tests which
do not use this API and which do not declare any subtests will soon be
reported as a harness error.
Update some tests which previously opted in implicitly to use the new
API. Update others to instead declare a single subtest (so that they are
no longer single-page tests).
[1] https://github.com/web-platform-tests/wpt/pull/19449
[2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
--
wpt-commits: efe71da0885bec25ff8466160abd4bce44bbb2f8
wpt-pr: 19918
Differential Revision: https://phabricator.services.mozilla.com/D53542
Automatic update from web-platform-tests
[css-text] Consider breaking opportunities of inline siblings
First of all, bear in mind that this change affects only to
intrinsic size computation in legacy layout.
During the intrinsic size computation of blocks with inline children,
we are determining the breaking opportunities for each child. When the
word-break: break-word is used, each of this breaking opportunities
should account for the min-content size.
We only consider breakable locations for start and end if they are
br elements or spaces, under auto-wrap, to compute the intrinsic size
of a box. This is fine, since we are already using a break iterator
to determine the min-size of each word. However, we were incorrectly
summing the first_line_min_width for each inline sibling, even when
they were part of the same text line.
This change tries to avoid that problem by assuming that there is
always a breaking opportunity after every character, since the
spec now states that break-word should behave as normal and
overflow-wrap: anywhere.
Bug: 1013644
Change-Id: I04261b323cd029a624724363a566fccc826863af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1856959
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Cr-Commit-Position: refs/heads/master@{#710359}
--
wpt-commits: 87d9d891e4f0c2276cc4ad4bbd7e101a7c9b05d9
wpt-pr: 19651
Differential Revision: https://phabricator.services.mozilla.com/D53540
haozhe
Chris Harrelson
autofoolip
moz-wptsync-bot
Oriol Brufau
Philip Jägenstedt
Stephen McGruer
Leon Han
Kai Ninomiya
Xiaocheng Hu
Eric Willigers
jugglinmike
Robert Ma
Hiroshige Hayashizaki
Pablo Saavedra
pyup.io bot
Nicolás Peña Moreno
Francois Beaufort
Stefano Sanfilippo
Rune Lillesveen
Adam Rice
Joey Arhar
Daniel Clark
Javier Fernandez
Koji Ishii
Yi Gu
Simon Pieters
Sam Sneddon