We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<details>
<summary>
The WebKit implementation of those elements is completely out of date, and causes a lot of pain for web developers:
Also add support for ::details-content
https://html.spec.whatwg.org/#the-details-and-summary-elements
WebKit: WebKit/standards-positions#351 Gecko: mozilla/standards-positions#1027
See: https://bugs.webkit.org/showdependencytree.cgi?id=252223&hide_resolved=1
There were some mentions in State of HTML/CSS
The text was updated successfully, but these errors were encountered:
::details-content has shipped in Chrome 131 and introduces a new concept: part-like pseudo-elements.
::details-content
This means that selectors such as the following are valid:
Sorry, something went wrong.
No branches or pull requests
Description
The WebKit implementation of those elements is completely out of date, and causes a lot of pain for web developers:
Also add support for ::details-content
Specification
https://html.spec.whatwg.org/#the-details-and-summary-elements
Additional Signals
Standards Positions
WebKit: WebKit/standards-positions#351
Gecko: mozilla/standards-positions#1027
Site breakage and workaround
Browser Bugs
Likely Compatibility Impact
See: https://bugs.webkit.org/showdependencytree.cgi?id=252223&hide_resolved=1
Developer surveys
Other Developer Sentiment
There were some mentions in State of HTML/CSS
The text was updated successfully, but these errors were encountered: