- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 Jan 2025 19:10:22 +0000
- To: public-css-archive@w3.org
> Something that is not defined yet is what should happen when the input for ident() is invalid. Nope, that's perfectly defined already - the function is invalid because it doesn't match the specified grammar. (And because that happens due to var() substitution, it's IACVT rather than a parse failure.) I don't think we really need a fallback here. In general, CSS functions don't guard against the possibility of some argument being invalid from a nonsense var() substitution. I'm not seeing anything special about ident() that would make it more necessary to add special handling. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11424#issuecomment-2610807685 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 23 January 2025 19:10:22 UTC