-
Notifications
You must be signed in to change notification settings - Fork 711
[css-view-transitions-2] Consider allowing ::view-transition-group(.class)
without *
#9874
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
Probably to go with #9626 as well |
Right. I believe (if I am incorrect, please re-open this issue) |
This is a separate issue. #9972 only dealt with This issue is about allowing |
The CSS Working Group just discussed
The full IRC log of that discussion<keithamus> vmpstr: we have VT pseudo elements. They take a name param, or universal selector *. We also added vt classes that specify a name and set of classes that are written as .foo.bar.<fantasai> +1 to allowing the * to be dropped <keithamus> vmpstr: because of the syntax currently specified, universal selector with class you need to spell out *.foo. We'd like to resolve to have * optional if you're using class param. Would look similar to how CSS looks with .class. Other point is that if we dont have a class, Id prefer to require a * - not requiring () <fantasai> +1 to the proposal <keithamus> emilio: how are they defined? Selector syntax? Or custom <keithamus> vmpstr: custom <keithamus> khush: args to pseudo element <keithamus> vmpstr: yes, syntax to the arg is specified in VT spec <keithamus> astearns: you're talking about omitting * if using class? This is not just optionally omitting but making *.class syntax invalid? <keithamus> vmpstr: no, optionally <khush> +1 <keithamus> PROPOSED RESOLUTION: Make * optional if you are using a class. <emilio> Sgtm <keithamus> RESOLVED: Make * optional if you are using a class. <keithamus> astearns: also omitting parens entirely? <keithamus> vmpstr: the way the resolution is phrased Im happy. If its optional altogether Id like it to not be optional. This resolution satisfies that. <keithamus> astearns: can scroll go to next week or? <keithamus> fantasai: no, this one is about alignment property. |
Based on resolution: w3c#9874 (comment) Closes w3c#9874
…0153) Based on resolution: #9874 (comment) Closes #9874
I guess whitespaces are invalid between tokens matching these productions.
Would it be possible to clarify it explicitly (like for selector productions), and add a whitespace between |
This would be consistent with how class selectors work outside of view-transitions.
The text was updated successfully, but these errors were encountered: