Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[mediaqueries][color] dynamic-range is a really ambiguous term and doesn't mention it's about color #9957

Open
fantasai opened this issue Feb 14, 2024 · 6 comments
Labels

Comments

@fantasai
Copy link
Collaborator

dynamic-range is totally not clear that it's about color, it should have the word "color" in it.

@dbaron
Copy link
Member

dbaron commented Feb 14, 2024

This initially came up in the WG discussion we just had about #9074.

@frivoal
Copy link
Collaborator

frivoal commented Feb 14, 2024

I disagree. Technically, yes, dynamic range could apply to any quantity: from sound amplitude, to voltage of an electric signal, to frequency of an electromagnetic wave…

But css-speech non withstanding, CSS is largely a visual medium. And when speaking of visual things, there's very little ambiguity about what dynamic range refers to. Whether it's camera specifications, TV sales brochures, modes in the camera app on everyone's phone, the characteristics of camera film, printing… everybody just talks about (high) dynamic range, without "color" or any similar qualifier.

And if you wanted to really disambiguate, "color" is still too vague, as colors are a bundle of multiple quantities, and arguably, wide gamut could be described as high chromaticity dynamic range, and that's not what we're talking about here. So if we do want to disambiguate, we ought to go with brightness (or lightness, or luminance) dynamic range.

Not only is it non ambiguous in practice, it's also very discoverable, because (unqualified) dynamic range is the terminology everybody uses to talk about this matter. So I don't think additional qualifiers would help.

@svgeesus
Copy link
Contributor

Similarly, from a theoretical purity perspective, the color property should be foreground-fill-color. But the spec describes that quite well, so the property name can be short:

This property specifies the primary foreground color of the element. This is used as the fill color of its text content

So I don't think we need a non-Web-compatible name change to peak-luminance-dynamic-range or whatever. Just describe it clearly in the specification.

@svgeesus
Copy link
Contributor

So, close?

@svgeesus
Copy link
Contributor

So I don't think we need a non-Web-compatible name change to peak-luminance-dynamic-range or whatever. Just describe it clearly in the specification.

Now defined clearly

@astearns astearns removed the Agenda+ label Apr 2, 2024
@astearns
Copy link
Member

astearns commented Apr 2, 2024

@fantasai please close if you are satisfied with the discussion so far, or add more argument here for your position.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5 participants