Re: [csswg-drafts] [css-properties-values-api] Are fallbacks provided for registered properties validated by the CP syntax? (#10455)

The CSS Working Group just discussed `[css-properties-values-api] Are fallbacks provided for registered properties validated by the CP syntax?`, and agreed to the following:

* `RESOLVED: Drop validation of fallbacks wrt their custom property.`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> kizu: We have weird behavior which is surprisingly interoperable but not strictly defined<br>
&lt;fantasai> kizu: If we use a registered custom property that validates its value, but use it in a different property, and use var(--foo, fallback) and provide a fallback which is not accepted by this custom property<br>
&lt;fantasai> kizu: the result is ??? in all browsers<br>
&lt;fantasai> s/???/unset/<br>
&lt;fantasai> kizu: basically it is validated by the custom property, not by the property it's applied to<br>
&lt;fantasai> kizu: in the comments Oriol and Tab agree that we should remove this restriction<br>
&lt;emilio> q+<br>
&lt;astearns> ack emilio<br>
&lt;fantasai> fantasai: The fallback should validate against the property, not the custom property<br>
&lt;fantasai> emilio: +1 to removing this restriction. Also need to do more work for fallbacks.<br>
&lt;fantasai> astearns: removing would match the spec?<br>
&lt;fantasai> kizu: no, opposite. Implementations do what nobody expects.<br>
&lt;fantasai> kizu: But not useful.<br>
&lt;fantasai> emilio: Implementations match the spec, just spec is bad.<br>
&lt;fantasai> emilio: don't expect compat risk, we should try to change<br>
&lt;fantasai> PROPOSED: Drop validation of fallbacks wrt their custom property.<br>
&lt;fantasai> RESOLVED: Drop validation of fallbacks wrt their custom property.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10455#issuecomment-2402837489 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 9 October 2024 16:55:01 UTC