- From: Keith Cirkel via GitHub <noreply@w3.org>
- Date: Fri, 18 Jul 2025 11:57:13 +0000
- To: public-css-archive@w3.org
Thanks for the guidance all! I wonder if there is a way for implementations to discover this in a more robust manner? It seems a little unfortunate that one has to resolve types all the way down to find if there is a `<custom-ident>` production, and only then resolve to re-order the parsing steps to ensure that any type that is a supertype of `<custom-ident>` should be parsed last. It seems like it's an opportunity for bugs to sneak in. (If I were CSS BDFL I might consider adding some kind of "type coloring" sigil do denote types that should have a lower precedent, and such a sigil would be contagious, so something like `<single-transition-property>` would also need to be marked accordingly). At any rate I'll make a PR for the additional wording. -- GitHub Notification of comment by keithamus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12494#issuecomment-3089242825 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 July 2025 11:57:14 UTC