Track Anchor Positioning anchor names and rects during abspos reflows
Categories
(Core :: Layout: Positioned, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox143 | --- | fixed |
People
(Reporter: jwatt, Assigned: dshin)
References
(Blocks 1 open bug)
Details
(Whiteboard: [anchorpositioning:m1])
Attachments
(3 files)
During reflow we want to keep track of the anchors that are used by an Anchor Positioned element, and the rects of those anchors relative to the anchor positioned frame. We'll need suitable invalidation for this cached information.
Updated•2 months ago
|
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Comment 1•28 days ago
|
||
Upcoming change adds a new frame property that will save this. Manipulating
the frame property requires non-const nsIFrame
pointer, which is not ideal
given that that instantiation sites of resolution parameters often are const
qualified. Ideally, we avoid adding const casts, so we add a separate field
to act as a cache.
Abspos frames that may reference anchors have a clear, single reflow site
in nsAbsoluteContainingBlock
, which keep things simple.
Non-abspos frames that reference anchors will always have their references
resolve to be invalid - If they switch to abspos, they need to be moved or
reconstructed anyway, so we don't have to worry about them.
Assignee | ||
Comment 2•28 days ago
|
||
Since we need to track and store anchor references anyway, this ends up being
a neat side effect. It is assumed that the cached storage is provided afresh
whenever a new reflow happens, so that we avoid using stale anchor references.
Assignee | ||
Comment 3•28 days ago
|
||
Updated•23 days ago
|
Comment 5•18 days ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/0aa660fda704
https://hg.mozilla.org/mozilla-central/rev/ff3ff4420c7a
https://hg.mozilla.org/mozilla-central/rev/cd58755162c4
https://hg.mozilla.org/mozilla-central/rev/81140ebea290
Description
•