Re: [csswg-drafts] [css-values-4] Switch advanced attr() to being var()-like (#4482)

The CSS Working Group just discussed `[css-values-4] Switch advanced attr() to being var()-like`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-values-4] Switch advanced attr() to being var()-like<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4482<br>
&lt;dael> TabAtkins: I finished the edits to re-write and they're in Values 4 ED. I put attr() in its own section. mostly cribbed from var spec. I have a note to re-write substitution algo.<br>
&lt;AmeliaBR> commit for changes: https://github.com/w3c/csswg-drafts/commit/ed7beac806cc4753d8134857ff526150bb2a631c<br>
&lt;dael> TabAtkins: Otherwise it works similar to old. You give a type, checkes if the attribute exists, and subsitutes in if it does. Assume valid at parse time. If it fails when you put it in it's invalid at computed value time.<br>
&lt;dael> TabAtkins: Our impl thinks it's reasonable. If anyone else wants to look it would be great.<br>
&lt;dael> TabAtkins: Only poss controversy is spec what type the value is, doing parsing on it. If you say color it's recognized as a color. Want to keep b/c attributes messier channel. Easier to mess with, scripts sometimes write them. Ensuring a valid thing comes out and then switch to default seems valuable here.<br>
&lt;dael> TabAtkins: I'm happy with current. Any further comments or strong opinions please give them here or in issue.<br>
&lt;dael> TabAtkins: I'll ask for resolution to approve next week.<br>
&lt;dael> Rossen_: Thanks.<br>
&lt;dael> Rossen_: Action on everyone who cares about these changes to review so we can discuss on next call.<br>
&lt;florian> +1 to the design goals. Will review details<br>
</details>


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

Received on Wednesday, 11 December 2019 17:11:55 UTC