1299310 - Extend eCSSUnit_RGBColor/eCSSUnit_RGBAColor to store values out of the range of [0, 255].

Status: NEW

(Core :: CSS Parsing and Computation, defect, P3)

Description

[Hiroyuki Ikezoe (:hiro)]

In bug 1295107, we are going to extend eCSSUnit_PercentageRGBAColor and eCSSUnit_PercentageRGBColor.  This bug is for eCSSUnit_RGBColor/eCSSUnit_RGBAColor.

Comment 1

[Hiroyuki Ikezoe (:hiro)]

Oops, sorry.  Filed against a wrong component.

Comment 2

[Daniel Holbert [:dholbert]]

This change is for this piece of spec-text in css-color-4:
 Values outside these ranges are not invalid, but are clamped to the ranges defined here at computed-value time.
https://drafts.csswg.org/css-color/#rgb-functions

I'm marking this as "depends-on" bug 1295456, where we're making a bunch of other css-color-4 changes.  (If we were feeling super-ambitious we might fix this as *part of* bug 1295456, but I think it's a big enough change that it deserves its own bug & can happen after bug bug 1295456.)

Comment 3

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Duplicate of bug 515919?

Comment 4

[Daniel Holbert [:dholbert]]

Sort of; let's consider this and bug 1295107 as pieces of bug 515919.

Also: we should similarly update hsl() parsing to accept out-of-range saturation, lightness, & alpha values, too. (I suspect we already don't clamp for "hue", though I'm not sure.)  The css-color-4 spec doesn't say anything specifically about allowing out-of-range values for hsl, right now -- but presumably the same spec-text from comment 2 should apply for hsl() components.

The hsl changes would probably want to be in a separate patch from the rgb() changes, though it could be on this bug or on its own other bug (which would also block bug 515919).