- From: Westbrook Johnson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Oct 2024 00:17:49 +0000
- To: public-css-archive@w3.org
A style lookup to resolve `.part` would certainly be unfortunate...though would it be prohibative? Multiple parts is a great point, an approach like this would need to not reduce the API surface, meaning it would need to accept multiple. This of course adds a couple of new "Potential issues": - there's no such thing as merged property values, to the best of my knowledge, so if you wanted `<button class="thing-1 thing-2">` to have multiple parts, one because of the class `thing-1` and another because of `thing-2`, there is likely no path to making that possible, at least not without additional changes to the underlying APIs of CSS - in practice this approach to applying multiple part names would likely also suffer from the same issue that lead to `transform` being broken in `scale`, `translate`, et al, the inability to easily edit one of the many values of the property. Hrm...but the symmetry with `view-transition-name` is so nice. -- GitHub Notification of comment by Westbrook Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10988#issuecomment-2387304813 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 October 2024 00:17:50 UTC