When anchor has IB-split, anchor() and anchor-size() consider only the first inline fragments
Categories
(Core :: Layout: Positioned, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox157 | --- | fixed |
People
(Reporter: TYLin, Assigned: TYLin)
References
(Blocks 1 open bug)
Details
(Keywords: webcompat:platform-bug, Whiteboard: anchor-positioning-transform-triage, [wptsync upstream])
User Story
user-impact-score:100
Attachments
(2 files)
Load the attached Testcase #1.
Expected results:
The green rectangle covers all the text. Google Chrome and Safari both have the expected results.
Actual results:
The green rectangle covers only "ipsum dolor".
| Assignee | ||
Updated•20 days ago
|
Updated•18 days ago
|
Updated•17 days ago
|
| Assignee | ||
Comment 1•11 days ago
|
||
This allows an anchor element that is IB-split to return a correct
union rect so that anchor functions resolve against the anchor's
entire bounding rect, rather than only the first inline fragment.
This patch follows Chrome's and Safari's behavior of unioning the
MozBlockInsideInlineWrapper rects. That is, we do not drill into
the wrapper to find the rects of the real block children.
anchor-position-inline-008.html tests that by adding explicit
width to the block child under anchor.
Note that calling getBoundingClientRect() for inline element that
has IB-split will drill into the block wrapper. This internal
inconsistency is tracked in Bug 2066179.
Updated•11 days ago
|
Comment 3•10 days ago
|
||
| bugherder | ||
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/62318 for changes under testing/web-platform/tests
Upstream PR merged by moz-wptsync-bot
Description
•