Releases: web-platform-tests/wpt
merge_pr_54216
Ensure avoid checking PrimaryFrame before IsHostIsSlot for next tabbable
In GetNextTabbableContentInScope we iterate over content, trying to find
the next tabbable content within the scope. With the next peice of
iterable content we first check if it is IsInNativeAnonymousSubtree and
if it has a PrimaryFrame, and if so check that frames tabIndex. If the
element does not have a frame we then check the host/slot tabindex.
Finally if it's not a host/slot we check the primary frame (again).
This means for slots with a display:contents
value, they'll have no
frame and they'll drop to the next condition (IsHostIsSlot
), however
for slots with a frame (e.g. display:block
) they'll use the frames
tabIndex value.
For a slot element with display:block
this means we're reliant on the
primary frame's focusability, but this is an incorrect flow of logic
because it means that the slot with display:block is skipped - one such
element exists: the ::details-content
pseudo.
By simply removing this check, and letting the else
block resolve the
primary frame's tabIndex, we can correctly ensure ::detils-content
children can be focused.
Differential Revision: https://phabricator.services.mozilla.com/D260305
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1981724
gecko-commit: ac7effcd195408dea875aaf8867cbae687701ecf
gecko-reviewers: emilio
merge_pr_54212
partitioned-cookies/partitioned-cookies.tentative.https.html leaks cookies
Differential Revision: https://phabricator.services.mozilla.com/D260479
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1982046
gecko-commit: b9a5f75b6d3855420a1c70f1542986d074452b51
gecko-reviewers: valentin
merge_pr_54204
Digital credential: promise should reject if frame is destroyed (#54204)
-
Digital credential: promise should reject if frame is destroyed
-
Apply suggestions from code review
Co-authored-by: Copilot 175728472+Copilot@users.noreply.github.com
Co-authored-by: Copilot 175728472+Copilot@users.noreply.github.com
merge_pr_54225
Exclude anchor() and anchor-size() functions from MISU
These functions can become invalid at computed value time, even though
they are not substitution functions. MISU [1] is not able handle this,
so we just exclude those values.
[1] CL:3412160
Fixed: 436621815
Change-Id: Ifa8b57cf339911fbb8cdb9aba1a61f451a810a7d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6830645
Commit-Queue: Anders Hartvoll Ruud andruud@chromium.org
Reviewed-by: Steinar H Gunderson sesse@chromium.org
Cr-Commit-Position: refs/heads/main@{#1499331}
merge_pr_54221
WebKit export of https://bugs.webkit.org/show_bug.cgi?id=203770 (#54221)
merge_pr_54211
Cookie Store API: trimming of TAB and SPACE
merge_pr_54217
Writing Assistance APIs: Update unsupported language codes in WPTs
Fixed: 407988949
Change-Id: Icd7eefe17d37f02bee713204cb360c7d492fd2a6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6828698
Auto-Submit: Mike Wasserman msw@chromium.org
Commit-Queue: Mike Wasserman msw@chromium.org
Reviewed-by: Clark DuVall cduvall@chromium.org
Commit-Queue: Clark DuVall cduvall@chromium.org
Cr-Commit-Position: refs/heads/main@{#1498993}
merge_pr_54215
[gap-decorations] Interpolation with repeaters for *-rule-color
This CL implements Interpolation for *-rule-color for repeaters.
In order to handle repeaters, we add a new InterpolableType
InterpolableGapDataRepeater
which handles interpolation for repeaters
by essentially keeping a member InterpolableList of the values in the
repeater and interpolating those individually through that type.
The overall structure of interpolation for gap decorations will be as
follows:
CSSGapLengthListInterpolationType
handles interpolation for
GapDataList
We then hand off the actual interpolation with an
InterpolableList
of InterpolableLength
,
InterpolableGapDataRepeater
(which itself contains an
InterpolableList
of InterpolableLengths
) and InterpolableColor
.
InterpolableGapDataRepeater is templated, in order to handle for
interpolation for column/row-rule-color as well as width.
For now we are implementing mirroring the behavior of grid-template
interpolation (which can be a list of values with repeaters), in which
we only interpolate if the length of the lists match. If this changes
after spec discussions then the test will be updated.
https://www.w3.org/TR/css-gaps-1/#lists-repeat
Bug: 357648037, 419066541
Change-Id: I317b0c059a901d8eafa722aa71b878c4ecde3eda
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6734136
Commit-Queue: Javier Contreras javiercon@microsoft.com
Reviewed-by: Robert Flack flackr@chromium.org
Cr-Commit-Position: refs/heads/main@{#1498969}
merge_pr_54214
[gap-decorations] Change rule-paint-order
to rule-overlap
This CL updates the property to the new name as per the resolution
in w3c/csswg-drafts#12540.
Bug: 357648037
Change-Id: I921849351e9b31609a1120a3a96e3c75d0268bbe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6829006
Reviewed-by: Alison Maher almaher@microsoft.com
Commit-Queue: Javier Contreras javiercon@microsoft.com
Cr-Commit-Position: refs/heads/main@{#1498954}
merge_pr_54210
Unify paths for constructing the style sheet list.
We used to have three different ways of constructing the DOM-visible
style sheet list (document.styleSheets), and one of them (the one
for documents) would mistakenly include adopted style sheets as part
of the list. This meant that document.styleSheets could differ
depending on whether we had recently updated RuleSets or not.
Make every path call the existing fast path (the one that only
constructs this list, not RuleSets and such), fixing the problem.
Also, add a test.
Fixed: 437259105
Change-Id: Ida596657053af3a4a380ac5909f9fc6ed011a97d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6832391
Commit-Queue: Steinar H Gunderson sesse@chromium.org
Reviewed-by: Rune Lillesveen futhark@chromium.org
Commit-Queue: Rune Lillesveen futhark@chromium.org
Auto-Submit: Steinar H Gunderson sesse@chromium.org
Cr-Commit-Position: refs/heads/main@{#1498720}