Closed
Bug 1962471
Opened 9 months ago
Closed 3 months ago
Implement mechanism cache/store the result of `position-visibility` evaluation
Categories
(Core :: Layout: Positioned, enhancement)
Core
Layout: Positioned
Tracking
()
RESOLVED
DUPLICATE
of bug 1962472
People
(Reporter: dshin, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [anchorpositioning:m3])
For any element using position-visibility (And/or position-try-fallbacks), we need to store information on if the positioned element should remain visible, like we do for content-visibility: auto.
This information should be consulted by relevant abs-positioned elements to determine if they should be strongly hidden, which will be handled in bug 1962472
| Reporter | ||
Updated•9 months ago
|
Summary: Implement mechanism to evaluate `position-visibility` in at ResizeObserver event time → Implement mechanism to evaluate `position-visibility` at ResizeObserver event time
| Reporter | ||
Updated•9 months ago
|
| Reporter | ||
Updated•9 months ago
|
| Reporter | ||
Updated•9 months ago
|
Assignee: nobody → dshin
Status: NEW → ASSIGNED
Updated•9 months ago
|
Whiteboard: [anchorpositioning:triage] → [anchorpositioning:m2]
| Reporter | ||
Updated•5 months ago
|
Updated•4 months ago
|
Assignee: dshin → nobody
Status: ASSIGNED → NEW
Updated•4 months ago
|
Whiteboard: [anchorpositioning:m2] → [anchorpositioning:reserve]
| Reporter | ||
Comment 1•4 months ago
|
||
(Adding discussions with :tlouw from bug 1953529 work)
To be called from probably ShouldSkipFrame or similar.
That is a hot path, and frame property may slow us down with its consistent linear lookups. Frame bits are ideal but we're out of space there. Maybe we can recycle one?
Comment 2•3 months ago
|
||
The fix of bug 1962472 was determined to be enough to not require this any more. Could be reopened if needed.
Updated•3 months ago
|
Whiteboard: [anchorpositioning:reserve] → [anchorpositioning:m3]
You need to log in
before you can comment on or make changes to this bug.
Description
•