Closed Bug 2060557 Opened 3 months ago Closed 3 months ago

[wpt-sync] Sync PR 61721 - Resolve text-decoration-inset overflow and percentages precisely

Categories

(Core :: Layout: Text and Fonts, task, P4)

task

Tracking

()

RESOLVED FIXED
155 Branch
Tracking Status
firefox155 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 61721 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/61721
Details from upstream follow.

Helmut Januschka <helmut@januschka.com> wrote:

Resolve text-decoration-inset overflow and percentages precisely

Replace the conservative text-decoration-inset ink overflow bounds with
exact bounds: overflow computation now receives the same fragment
context as painting (a line cursor positioned at the current fragment
plus its neighboring fragments), so inset trims and expansions match
the painted decoration exactly. Conservative bounds remain for
marker-driven highlight overflow paths: text-decoration-inset is valid
on highlight pseudo styles, but those paths have no fragment context.

Percentage insets with box-decoration-break: slice now resolve against
the total inline size of the decorated run instead of the individual
fragment, by walking the fragment chain in both directions, across
soft-wrapped lines and forced breaks inside the run. Run-edge trims
carry into following or preceding fragments when they exceed a fragment
size, which makes the previously failing WPT tests
text-decoration-inset-028 and -030 pass.

Add unit coverage for run-based percentage resolution and inset
accumulation, WPT reftests for single-line and wrapped fragmented runs,
and a WPT invalidation reftest that adds and removes insets (including
negative insets extending beyond the text) after the initial paint.

Bug: 539095434, 498974811
Binary-Size: Size increase is unavoidable
Change-Id: I56187b052f7e3eadd8cf7eaf5410772d6edc7491
Fixed: 539095434
Reviewed-on: https://chromium-review.googlesource.com/8148940
WPT-Export-Revision: 02c14d8c38d434050c9f1b142005256bc7646ad5

Component: web-platform-tests → Layout: Text and Fonts
Product: Testing → Core

CI Results

Ran 11 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 362 tests

Status Summary

Firefox

OK : 48
PASS: 2[GitHub] 9[Gecko-linux2204-64-wayland-debug, Gecko-linux2204-64-wayland-opt] 1290[Gecko-windows11-32-25h2-debug, Gecko-windows11-32-25h2-opt] 1574[Gecko-android-em-14-x86_64-debug-geckoview, Gecko-android-em-14-x86_64-lite-opt-geckoview, Gecko-android-em-14-x86_64-opt-geckoview] 1575[Gecko-linux2404-64-debug, Gecko-linux2404-64-opt] 1576[Gecko-windows11-64-25h2-debug, Gecko-windows11-64-25h2-opt]
FAIL: 1[GitHub] 11[Gecko-windows11-32-25h2-debug, Gecko-windows11-32-25h2-opt] 30[Gecko-windows11-64-25h2-debug, Gecko-windows11-64-25h2-opt] 31[Gecko-android-em-14-x86_64-debug-geckoview, Gecko-android-em-14-x86_64-lite-opt-geckoview, Gecko-android-em-14-x86_64-opt-geckoview, Gecko-linux2404-64-debug, Gecko-linux2404-64-opt]

Chrome

PASS: 2
FAIL: 1

Safari

PASS: 2
FAIL: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Tests Disabled in Gecko Infrastructure

Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → 155 Branch
You need to log in before you can comment on or make changes to this bug.