-
Notifications
You must be signed in to change notification settings - Fork 658
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-backgrounds-3] Computed values of background-repeat don't follow reality #1488
Comments
Note also that if one runs that sample with |
"Computed value" and "serialization" are distinct, unrelated concepts. Computed value is a CSS-internal concept used by the specs. The "shortest equivalent" rule is usually in effect for serializing computed values, which is why everyone serializes |
From what should I infer that when reading "A list, each item consisting of: two keywords, one per dimension" though? I don't understand why everyone should serialise to |
Because, as I said, "computed value" and "serialization" have nothing directly to do with each other. The serialization of the value is not specified in the propdef table; it's implicitly specified in CSSOM as the shortest equivalent serialization that'll produce the same value. The computed value is a pair of values. We can operate on that in spec text, asking what the horizontal background-repeat is, versus the vertical background-repeat. This avoids us having to go thru contortions in spec text to reproduce the effects of parsing, like "do X if the vertical repeat is Y, or if it's unspecified and the horizontal repeat is Y". |
I see. Closing. |
The spec says:
But Safari, Chrome and Firefox do otherwise and just serialise computed values as specified.
The text was updated successfully, but these errors were encountered: