Open
Bug 1418138
Opened 7 years ago
Updated 6 months ago
Make display: contents work for ::before and ::after
Categories
(Core :: CSS Parsing and Computation, enhancement, P3)
Core
CSS Parsing and Computation
Tracking
()
NEW
People
(Reporter: emilio, Unassigned)
References
(Blocks 2 open bugs, )
Details
(Keywords: parity-chrome, parity-safari)
Per https://github.com/w3c/csswg-drafts/issues/1345, they should. WebKit implemented it using an anon inline box, which is a nice way to do it, since there are only other inlines in the generated content (so it's not observable).
|
Reporter | |
Comment 1•7 years ago
|
||
Over to the queue of "would like to work on, eventually" :)
Flags: needinfo?(emilio)
|
||
Updated•7 years ago
|
Priority: -- → P3
|
|
Reporter | |
Comment 2•6 years ago
|
||
I don't think this is prioritary enough to warrant a ni?.
Flags: needinfo?(emilio)
|
||
Updated•2 years ago
|
Severity: normal → S3
|
||
Comment 3•6 months ago
•
|
||
This should (at least partially) be why we're failing the WPTs:
- https://wpt.fyi/results/css/css-display/display-contents-dynamic-before-after-001.html
- https://wpt.fyi/results/css/css-display/display-contents-dynamic-before-after-first-letter-001.html
Chrome and Safari both pass them.
Blocks: 1887054
|
|
||
Updated•6 months ago
|
Keywords: parity-chrome,
parity-safari
You need to log in
before you can comment on or make changes to this bug.
Description
•