-
Notifications
You must be signed in to change notification settings - Fork 715
[css-values-4] Punt attr() and toggle() to Level 5 #6753
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Given #6764, |
Should |
@Loirooriol No, we need that one to handle serialization of interpolation of transforms. |
The CSS Working Group just discussed
The full IRC log of that discussion<dael_> Topic: #6753<fantasai> github: https://github.com//issues/6753 <dael_> fantasai: We think we should drop from L4. attr() and toggle(). not quite solid. A bunch of the rest of the spec has been impl <dael_> fantasai: Narrowing spec to prep for CR <dael_> Rossen_: Obj? <dael_> oriol: Question on this. I wonder if mix should also be deferred. Added recently and issues about syntax <dael_> fantasai: I think problem with mix is need it to serialize interpolation of certain transforms. I think we should keep it and work out the issues <dael_> oriol: Okay <dael_> Rossen_: Hearing no objections <dael_> RESOLVED: Punt attr() and toggle() to Level 5 <fantasai> oriol, we kept it simple though, and are pushing all the more complex interpolations to L5 |
Given that |
I don’t really disagree, but this idea was basically rejected in #3702. |
The question is how to get implementer interest because author interest is definitely there regarding its many use cases. Sebastian |
Tab and I think it's time to start preparing css-values-4 for CR, as a lot of the stuff in here is already implemented (and shipped!). We think it would make sense, however, to cut ''attr()'' and ''toggle()'' and push them to Level 5. Agenda+ to ask about doing this.
The text was updated successfully, but these errors were encountered: