Skip to content
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

[css-values-4] Punt attr() and toggle() to Level 5 #6753

Closed
fantasai opened this issue Oct 21, 2021 · 7 comments
Closed

[css-values-4] Punt attr() and toggle() to Level 5 #6753

fantasai opened this issue Oct 21, 2021 · 7 comments

Comments

@fantasai
Copy link
Collaborator

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.

@Loirooriol
Copy link
Contributor

Given #6764, toggle() doesn't seem ready for CR. I support deferring it to L5.

@Loirooriol
Copy link
Contributor

Should mix() also be deferred to L5?

@fantasai
Copy link
Collaborator Author

fantasai commented Nov 3, 2021

@Loirooriol No, we need that one to handle serialization of interpolation of transforms.

@css-meeting-bot
Copy link
Member

The CSS Working Group just discussed #6753, and agreed to the following:

  • RESOLVED: Punt attr() and toggle() to Level 5
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

@SelenIT
Copy link
Collaborator

SelenIT commented Dec 17, 2021

Given that attr() has been there since at least 2005 and keeps being deferred because of no implementation signal, shouldn’t it be reconsidered more deeply? The existing situation seems much like the lack of implementers’ interest. Perhaps the attr() function should forever stay in the string-only form as defined in CSS2.x, and for deriving typed values from attributes something new should be introduced instead, to avoid confusion and make experimenting/implementation easier?

@Crissov
Copy link
Contributor

Crissov commented Dec 17, 2021

I don’t really disagree, but this idea was basically rejected in #3702.

@SebastianZ
Copy link
Contributor

The question is how to get implementer interest because author interest is definitely there regarding its many use cases.

Sebastian

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

6 participants