Skip to content
New issue

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

improved styling of <details> and <summary> elements #351

Closed
dbaron opened this issue May 22, 2024 · 2 comments
Closed

improved styling of <details> and <summary> elements #351

dbaron opened this issue May 22, 2024 · 2 comments
Assignees
Labels
position: support topic: css Spec relates to CSS (Cascading Style Sheets) topic: html Spec relates to HTML (Hypertext Markup Language) venue: Open UI CG venue: W3C CSS WG venue: WHATWG HTML Workstream

Comments

@dbaron
Copy link

dbaron commented May 22, 2024

WebKittens

@annevk

Title of the spec

improved styling of <details> and <summary> elements

URL to the spec

Not a single spec, but a set of changes initially discussed in openui/open-ui#744 and now moved to w3c/csswg-drafts#9879 and whatwg/html#10265 for the parts that belong in CSS and HTML respectively.

URL to the spec's repository

No response

Issue Tracker URL

No response

Explainer URL

https://github.com/dbaron/details-styling

TAG Design Review URL

https://github.com/w3ctag/design-reviews/issues/TBD

Mozilla standards-positions issue URL

mozilla/standards-positions#1027

WebKit Bugzilla URL

No response

Radar URL

No response

Description

This is a proposal to add some features to both CSS and HTML (and additional precision to HTML) to make the details and summary elements more easily styleable by authors.

@hober hober added topic: css Spec relates to CSS (Cascading Style Sheets) topic: html Spec relates to HTML (Hypertext Markup Language) labels May 22, 2024
@karlcow
Copy link
Member

karlcow commented May 23, 2024

@annevk
Copy link
Contributor

annevk commented May 27, 2024

Making these elements better stylable makes a lot of sense. I suggest we resolve this as "position: support" one week from now.

I left these comments in the course of my review:

  • ::details-content vs display: contents might make them hard to remember, but that's probably a lost cause.
  • If the text is generated by the user agent, it should probably adhere to the language of the node rather than the end user's chosen language. But that's an existing issue and can be follow-up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
position: support topic: css Spec relates to CSS (Cascading Style Sheets) topic: html Spec relates to HTML (Hypertext Markup Language) venue: Open UI CG venue: W3C CSS WG venue: WHATWG HTML Workstream
Projects
None yet
Development

No branches or pull requests

4 participants