- From: Nick Williams via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Sep 2024 09:01:12 +0000
- To: public-css-archive@w3.org
> Every use case I’ve seen where multiple part names are used, only one is actually a true part name, and the others are states which are better addressed as custom pseudo-classes. @LeaVerou an example where I have used multiple parts - I have a calendar component with lots of `<button>`s (next month, previous month, plus every day is a button). Each of these has a `button` part. This allows consumers to apply broad styles to all buttons. But also each button has more specific parts like `next`, `previous`, `day`. Allowing users to style individual instances (next/previous) or categories of buttons (days). So there are two parts on each, they are always present, and neither are state related. -- GitHub Notification of comment by WickyNilliams Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9951#issuecomment-2348419415 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 13 September 2024 09:01:13 UTC