Skip to content

Do we need to match CSS achromatic threshold? #465

@facelessuser

Description

@facelessuser

Recently, we made a change to scale achromatic threshold by order of magnitude. This means that a color that scales achromatic chroma roughly, not precisely, between 0 - 1 would have an achromatic threshold of 1e-6 vs a color that scales in the 100s which would be 1e-4.

CSS seems to be proposing an approach that may make it into the actual CSS spec that wants to use the reference range divided by 100,000. This isn't too dissimilar to what we are doing now as though it is a much more relaxed threshold which will yield a an epsilon of 1e-3 for 0 - 100 and 1e-5 for 0 - 100.

Additionally, the CSS approach is a little arbitrary in the sense that it is based on the reference range of the space. For instance, lab-like spaces are not all using the same reference gamut, so spaces like JzCzhz is scaled to look for an achromatic threshold relative to Rec. 2100 and LCh is scaled to look for an achromatic threshold relative to display-p3.

As an example, if using the CSS proposed approach, you are looking to see if chroma is below 0.0015 in LCh using a Display-P3 gamut as reference. If we were to use Rec2020 as the reference (which CSS doesn't), you would have a threshold of 0.00195. Not a huge difference, but a difference.

Our current approach tightens the threshold, but does so with the only caring about the order of magnitude of the values, and less about the precise range of a reference gamut.

I suspect this may be an area of CSS we care very little about, but something we should at least formally make a decision about.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P: maybePending approval of low priority request.T: featureFeature.skip-triageTells bot to not tag a new issue with 'triage'.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions