size containment should make replaced elements behave as if they were 0x0
Categories
(Core :: Layout, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox68 | --- | fixed |
People
(Reporter: dholbert, Assigned: dholbert)
References
Details
Attachments
(2 files)
I just noticed this in the size containment spec text:
Replaced elements must be treated as having an intrinsic width and height of 0.
https://drafts.csswg.org/css-contain/#containment-size
We need to implement this part.
Testcase attached, with some replaced elements all of which have contain:size and should be rendered with a content-box size of 0x0.
| Assignee | ||
Comment 1•6 years ago
•
|
||
For comparison, Chrome renders nearly every element in the testcase with a 0x0 content-box, with one exception: they render <audio controls> as a full-size audio widget -- this is a Chrome bug, because this element is definitely expected to be treated as a replaced element per https://html.spec.whatwg.org/multipage/rendering.html#embedded-content-rendering-rules :
The audio element, when it is exposing a user interface, is expected to be treated as a replaced element
(where I believe "exposing a user interface" means "has the controls attribute", basically)
I filed https://bugs.chromium.org/p/chromium/issues/detail?id=952414 on this Chrome bug.
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 2•6 years ago
|
||
| Assignee | ||
Updated•6 years ago
|
Updated•6 years ago
|
| Assignee | ||
Comment 3•6 years ago
|
||
| Assignee | ||
Comment 4•6 years ago
|
||
Note that Chrome doesn't quite pass the new WPT tests -- the first one (contain-size-replaced-003a.html ) fails due to the Chrome bug that I linked above:
https://bugs.chromium.org/p/chromium/issues/detail?id=952414
and the other two (003b.html and 003c.html) fail due to:
https://bugs.chromium.org/p/chromium/issues/detail?id=955163
Comment 6•6 years ago
|
||
| bugherder | ||
Description
•