- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 Feb 2023 10:56:07 +0000
- To: public-css-archive@w3.org
> In a math function, it resolves at parse time, when applicable, but Chrome/FF do not resolve it when they would not resolve a naked `<percentage>` at the same place. > > I think it is a bug [...] ..., on the other hand, resolving `<percentage>` in specified value seems to be only required for backward-compatibility of sRGB color functions, except for properties whose value is defined with `<alpha-value>` and I am not sure why this should be required for them. I am not a fan of simplifications of specified values. They can slow down parsing whereas they might not be used for rendering the document. Looking at the context for each `<percentage>` to figure out whether it can be resolved seems a bit complex. So imo the relevant question is whether or not all `<percentage>` should eagerly resolve to `<number>` in specified value, inside or outside math functions, when there is enough information to do it, or only the components of sRGB functions. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8485#issuecomment-1441555352 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 23 February 2023 10:56:08 UTC