- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Apr 2024 19:00:57 +0000
- To: public-css-archive@w3.org
Thanks @bkardell and @mayank99 for the effort to spot related discussions! Comments: - #2296 seems like it would improve the ergonomics of `@like`, but doesn’t really solve any of the same pain points unless the meaning of these selectors is somehow mutable (and would still be way more restricted) - #3596 same as above. This perhaps makes it easier to _target_ button-like and textbox-like controls, but not to style existing elements like them, unless authors universally adopt `:role(textbox)` and `:role(button)` for these styles (and I’m unsure if that’s the right solution as it seems to mix style and behavior — in most web apps there are buttons that look like buttons, and buttons that don't look anything like buttons, especially given the lack of good ARIA roles to describe today’s UIs. E.g. even interactive visualizations where you hover over a e.g. a pie chart wedge or scatterplot circle to see more info about that data have to use `role=button` because there’s nothing better. - #10094 That may be an interesting concept synergy, e.g. adopted styles could be imported as if part of the initial layer or something. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10222#issuecomment-2067131447 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 19 April 2024 19:00:57 UTC