[css-ui] Resolved value of caret-color should be the used value |
|||
Issue descriptionThis has been discussed by the CSS WG and resolved this week: https://github.com/w3c/csswg-drafts/issues/566 Basically caret-color will behave like the rest of color properties when you call getComputedStyle() to get the resolved value. Instead of getting "auto" or "currentcolor", you'll get the numeric value "rgb(X, X, X)". We need to update caret-color implementation, as current one is not passing: https://github.com/w3c/csswg-test/blob/master/css-ui-3/caret-color-009.html https://github.com/w3c/csswg-test/blob/master/css-ui-3/caret-color-013.html There's a CL doing that at: https://codereview.chromium.org/2577633002/
,
Jan 4 2017
Firefox is already returning a rgb() as resolved value, so we should update this too. There's a CL waiting for review: https://codereview.chromium.org/2577633002/ See Firefox bug for reference: https://bugzilla.mozilla.org/show_bug.cgi?id=1063162#c72
,
Jan 9 2017
This has been fixed by at r442214. https://chromium.googlesource.com/chromium/src/+/1d659157007dc8af77915b4af72f577b324c5e81 The CL pointed to bug #665422 instead of here, sorry about that. |
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Dec 24 2016