-
Notifications
You must be signed in to change notification settings - Fork 690
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
[cssom] Color properties should use "used value" as "resolved value" #566
Comments
Also that matches behavior of browsers which have implemented computed-value time |
Agenda+ because w3c/csswg-test#1161 is blocked by this. |
WG resolved to accept this. |
also clarified on call, no impact of this change on css3-color or css4-color. |
The WG resolved (ah!) in favor of making @therealglazou @zcorpan I think you guys are the editors, can you do the update? |
In the new CSS Color spec, computed value of
<color>
could be either a numeric color orcurrentcolor
keyword. However, color properties currently always return numeric color value, and web content may depend on that behavior. I think we should probably make those properties use "used value" as "resolved value" forgetComputedStyle
.The text was updated successfully, but these errors were encountered: