- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Feb 2024 22:45:36 +0000
- To: public-css-archive@w3.org
The current status is that all implementations create a replaced element when `content: <image>` is applied to a normal element, and create an inline replaced child when `content: <image>` is applied to `::before`. [testcase](https://www.software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cstyle%3E%0Ap.one%2C%20p.two%3A%3Abefore%20%7B%20content%3A%20url(http%3A%2F%2Fxanthir.com%2Fpony)%3B%20border%3A%20solid%3B%20padding%3A%201em%3B%20display%3A%20block%3B%20%7D%0A%3C%2Fstyle%3E%0A%0A%3Cp%20class%3D%22one%22%3E%0A%3Cp%20class%3D%22two%22%3E) Agenda+ to discuss: - Whether we want to make an exception for `::before` and `::after` specifically, or for all pseudo-elements. - Whether anyone wants to investigate the Web compatibility of migrating `::before` and `::after` to match regular elements. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2889#issuecomment-1928417269 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 5 February 2024 22:45:42 UTC