- From: carlosame via GitHub <sysbot+gh@w3.org>
- Date: Sat, 27 Feb 2021 14:45:08 +0000
- To: public-css-archive@w3.org
> the fallback syntax has _no benefit for CSS_, and _adds complexity and cost_ for no good reason Dropping the fallback looks like something desirable, but I do not see the fallback as something totally useless. Consider the following declaration: ```css color: rgb(...); color: color(--my-profile, ...); ``` In a browser that supports the `color()` function, the second value is valid at parse time, so the first one (the `rgb()`) is wiped out. If `--my-profile` fails for whatever reason when the value is computed, without the fallback it becomes _iacvt_ and the failure is likely to be important. If the fallback is dropped from the specification, I expect most `color()` functions with custom profiles to be used behind the protection of a `var()` fallback: ```css --my-color: color(--my-profile, ...); color: var(--my-color, rgb(...)); ``` I mean that dropping the fallback makes life a bit easier (at least for implementors), but leaves some fallout. -- GitHub Notification of comment by carlosame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5931#issuecomment-787082939 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 27 February 2021 14:45:10 UTC