Don't record a 0x0 last rememebered size when an element with `contain-intrinsic-size:auto` becomes `display:inline`
Categories
(Core :: Layout, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox106 | --- | fixed |
People
(Reporter: dholbert, Assigned: Oriol)
References
Details
Attachments
(1 file)
CSSWG resolved to not stomp on the last-recorded size when an element goes from display:block
to display:inline
(for consistency with what happens when the element goes from display:block
to display:none
).
https://github.com/w3c/csswg-drafts/issues/7606#issuecomment-1240015961
Oriol noted in the github issue that we (and Chrome) are currently recording 0x0 as the last-remembered size in this scenario, so we need an update to align with this resolution.
Reporter | ||
Comment 1•2 years ago
|
||
(Not sure if this needs a dedicated bug or not; Oriol, feel free to dupe if you're just handling this as part of existing work on other bugs. )
Reporter | ||
Updated•2 years ago
|
Assignee | ||
Comment 2•2 years ago
|
||
Should be quite straightforward, with just an edge case to consider: if the 0x0 size is not recorded due to display: inline
, and later the element becomes display: block
with size 0x0, then the last remembered size should be recorded even if a ResizeObserver wouldn't notify the change.
Updated•2 years ago
|
Assignee | ||
Comment 3•2 years ago
|
||
Comment 6•2 years ago
|
||
bugherder |
Description
•