Test parse-time HSL clamp of negative saturation to zero

[svgeesus]

See

• w3c/csswg-drafts@be48b10
• [css-color-4] Parse-time clip of HSL negative saturation for modern syntax? w3c/csswg-drafts#9222 (comment)

[dbaron]

Looks like it's not as interoperable as w3c/csswg-drafts#9222 (comment) suggests, since the new tests pass in Firefox but three of them fail in Chrome. Is that expected?

[svgeesus]

The new tests pass in Firefox but three of them fail in Chrome. Is that expected?

Not expected; the test values and expected values are from a test you wrote and the only difference is that your earlier CSS Color 3 test used legacy syntax, while the new addition to the CSS Color 4 test use modern syntax.

However I think the difference here is that Chrome is not accepting a mix of <number> and <percentage>, while Firefox is correctly allowing it for modern syntax. So that would be a Chrome bug.

[svgeesus]

Re-opened

• [css-color-4] Parse-time clip of HSL negative saturation for modern syntax? w3c/csswg-drafts#9222 (comment)

[svgeesus]

@dbaron this is seemingly a regression between Chrome 120 and Chrome 121 but I have made this PR a draft so CSSWG can decide on what behavior we want before this test change lands/doesn't land.

[dbaron]

Based on discussion in w3c/csswg-drafts#9222 this looks good.