-
Notifications
You must be signed in to change notification settings - Fork 636
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-anchor-position] is !important allowed in @position-try #10058
Labels
Comments
I assume disallowing means that declarations with |
Correct. |
The CSS Working Group just discussed
The full IRC log of that discussion<chrishtr> TabAtkins: are !important rules allowed in position-try?<chrishtr> TabAtkins: if they are then we'd have to define a new origin and not clear where that would go or what the use case is <Rossen_> ack fantasai <chrishtr> TabAtkins: propose the answer to the question is no <fantasai> https://www.w3.org/TR/css-animations-1/#keyframes <chrishtr> fantasai: agree it doesn't make sense, but we should be consistent with animations and how it's disallowed there <chrishtr> TabAtkins: it falls out of the way to say it's not allowed in the syntax <chrishtr> proposed resolution: !important is not allowed within position-try <chrishtr> RESOLVED: !important is not allowed within position-try |
tabatkins
added a commit
that referenced
this issue
Mar 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Should we allow
!important
decls in@position-try
? I'm inclined to say no - we're already having to do some slightly odd things with the cascade to make things work reasonably well and in a well-defined way (particularly withflip-*
keywords), so having some parts of the rule also apply in a separate!important
location would make it a lot more complicated for little, if any, benefit to authors.(And, like, where exactly would they go anyway? We resolved that normal decls here go at "the end of the author origin", and I'm inclined to actually specify that as a separate origin placed right after Author. Whether an "important position-try decl" should follow normal origin-reversing order (being weaker than author !important rules) or violate that to still go after the author !important rules would be an important decision, and both options are fairly bad, I think.)
So, propose to disallow !important.
The text was updated successfully, but these errors were encountered: