Fix bugs found in http://w3c-test.org/cssom/serialize-values.html |
|||||||
Issue description> Fail background-color: rgba(5, 7, 10, 0.5) assert_equals: background-color raw inline style declaration expected "rgba(5, 7, 10, 0.5)" but got "rgba(5, 7, 10, 0.498039)" This is issue 453414 . > Fail clip: rect(1em, auto, 0.5px, 2000em) assert_equals: clip raw inline style declaration expected "rect(1em, auto, 0.5px, 2000em)" but got "rect(1em auto 0.5px 2000em)" rect() should serialize with commas. "Append the result of invoking serialize a comma-separated list on list to s." https://drafts.csswg.org/cssom/#serialize-a-css-component-value > Fail content: counter(par-num) assert_equals: content raw inline style declaration expected "counter(par-num, decimal)" but got "counter(par-num)" This... is either a bug in the spec or a bug in the test. :-| "Let list be a list of CSS component values belonging to <counter>, omitting the last CSS component value if it is "decimal"." https://drafts.csswg.org/cssom/#serialize-a-css-component-value Filed spec issue https://github.com/w3c/csswg-drafts/issues/670 > Fail font-variant: normal assert_equals: font-variant raw inline style declaration expected "normal" but got "" > Fail outline-color: invert assert_equals: outline-color raw inline style declaration expected "invert" but got "" > (more similar failures) Not sure what's up with these.
,
Nov 2 2016
page-break-after properties -> bug 659297 outline-color: invert -> I think this is OK because UAs are allowed to not support invert? text-decoration properties (experimental flag on) -> bug 613451 font-variant: normal -> StylePropertySerializer bug probably? The 'none' keyword fails similarly.
,
Nov 2 2016
Filed issue about the test for outline-color: invert, https://github.com/w3c/web-platform-tests/issues/4143
,
Feb 13 2017
,
Oct 31 2017
Filed bug 779873 for clip() Filed bug 779874 for font-variant Still blocked on standards for the counter and outline-color issues
,
Dec 6 2017
,
Dec 6
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 12
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by shans@chromium.org
, Nov 1 2016Status: Available (was: Untriaged)