- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Sep 2024 00:55:18 +0000
- To: public-css-archive@w3.org
I agree that we should stick to the concept of part-like pseudo-elements. If we add an exception here, how many *other* exceptions will we add? How much working group time and implementor time will be spent implementing those exceptions, that could have been used for something else? And how much author confusion will result? I really do think that what we're trying to do here is to provide an author-facing model for complex built-in widgets that *exposes to developers* that these widgets are composed of more basic pieces of web technology. This has been the plan for a long time (>20 years) because it seemed like the only practical way to standardize the stylability of complex widgets, and I still think this is the case. I thought that the conclusion in https://github.com/w3c/csswg-drafts/issues/9951#issuecomment-1997897418 agreed with this concept but concluded that we would not use the name `::part()` because it was for author-built components and for standardized components that were built in to the Web platform. -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10775#issuecomment-2327704994 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 4 September 2024 00:55:19 UTC