[css-content] Implement 'content: none' for elements
Categories
(Core :: Layout, enhancement, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox91 | --- | fixed |
People
(Reporter: MatsPalmgren_bugz, Assigned: MatsPalmgren_bugz)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-complete)
Attachments
(2 files)
https://drafts.csswg.org/css-content/#valdef-content-none
On elements, this inhibits the children of the element from being rendered as children of this element, as if the element was empty.
...
In neither case does it prevent any pseudo-elements which have this element or pseudo-element as an originating element from being generated.
|
Assignee | |
Comment 1•3 years ago
|
||
Depends on D111707
|
||
Comment 2•3 years ago
|
||
There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:mats, could you have a look please?
For more information, please visit auto_nag documentation.
|
||
Updated•3 years ago
|
|
||
Comment 3•3 years ago
|
||
Once landed, this should be documented at https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Experimental_features#css.
Sebastian
|
|
Assignee | |
Comment 4•3 years ago
|
||
Pushed by mpalmgren@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/dcc1d0a10a11 [css-content] Implement 'content: none' for elements. r=emilio
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/29458 for changes under testing/web-platform/tests
|
||
Comment 7•3 years ago
|
||
| bugherder | ||
Upstream PR merged by moz-wptsync-bot
|
||
Comment 9•3 years ago
|
||
|
||
Comment 10•3 years ago
|
||
Pushed by aethanyc@gmail.com: https://hg.mozilla.org/integration/autoland/rev/715d1e5aebe0 Apply clang-format to nsCSSFrameConstructor.cpp. r=layout-reviewers,AlaskanEmily
|
||
Comment 11•3 years ago
|
||
| bugherder | ||
|
||
Comment 12•3 years ago
|
||
Once the PRs are merged this will be added to Experimental features and to BCD.
|
|
Assignee | |
Comment 13•3 years ago
|
||
FYI, this feature was disabled in bug 1719239 due to web-compat issues.
Filed spec issue: https://github.com/w3c/csswg-drafts/issues/6503
Description
•