-
Notifications
You must be signed in to change notification settings - Fork 683
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] <position> is a lie #1338
Comments
Yes, it's a recent decision (the April f2f meeting) to try and limit the usage of 3-value position as much as possible. We'll try and remove support for it from places where we can, and amend the definitions to explicitly use the 3-value-included production when proven necessary. |
@tabatkins Can I assume that the use sites I mentioned will be moved to |
As I said, if it proves necessary (that is, if compat prevents us from restricting them to the new |
Mmh, interesting, the 3-values syntax cannot be ambiguous in those sites, so why try to restrict them? |
Because it's a learning hazard. The 3-value syntax is basically a legacy mistake; there's no good reason to have it at all, and if we could remove it from every usage site, we would. |
Is there any intent from UAs to unship that syntax from the usage sites you have in mind? |
We're going to attempt that, yes. |
#2140 mentions progress in unshipping. |
The specification for
<position>
states that the 3-values syntax frombackground-position
is generically forbidden from it.This contradicts user agents in the wild, which all accept this supposedly-forbidden syntax everywhere
<position>
is used, such as in:mask-position
;-radial-gradient()
position.The text was updated successfully, but these errors were encountered: