Intent to Ship: CSS dynamic-range-limit property

[ccameron chromium]

Contact emails

ccam...@chromium.org, sbou...@google.com

Explainer

https://github.com/ccameron-chromium/hdr-headroom-limit/blob/main/EXPLAINER.md

Specification

https://drafts.csswg.org/css-color-hdr/#the-dynamic-range-limit-property

Summary

Enables a page to limit the maximum brightness of HDR content.

Blink component

Blink>CSS

TAG review

None

TAG review status

Not applicable

Risks

Interoperability and Compatibility

None

Gecko: No signal (https://github.com/mozilla/standards-positions/issues/979)

WebKit: No signal (https://github.com/WebKit/standards-positions/issues/312) WebKit engineers have expressed positive views of this proposal (it is similar to features available on macOS and iOS).

Web developers: Positive (https://github.com/w3c/csswg-drafts/issues/9074) Adobe has endorsed this proposal. Internal developers at Google have also requested this proposal.

Other signals:

Ergonomics

None.

Activation

None.

Security

None.

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

N/A

Debuggability

None

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?

Yes

Is this feature fully tested by web-platform-tests?

Yes. Extensive tests of CSS properties in wpt/css/css-color-hdr.

Full end-to-end testing requires observation on an HDR display. There does not yet exist a way to test high dynamic range (or wide color gamut) rendering: https://github.com/web-platform-tests/wpt/issues/44320

Flag name on about://flags

Experimental web platform features

Finch feature name

CSSDynamicRangeLimit

Requires code in //chrome?

False

Tracking bug

https://crbug.com/1470298

Availability expectation

Feature available on Web Platform in browsers as they add HDR image support (only Chromium supports HDR images so far).

Adoption expectation

Feature is requested by specific partners.

Non-OSS dependencies

Does the feature depend on any code or APIs outside the Chromium open source repository and its open-source dependencies to function?

No.

Sample links

https://ccameron-chromium.github.io/hdr-headroom-limit/example.html

Estimated milestones

Shipping on desktop	133
Shipping on Android	133
Shipping on WebView	133

Anticipated spec changes

No anticipated future spec changes.

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5146250411769856?gate=5206008539906048

Links to previous Intent discussions

Intent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGnfxj-m-wA4B%3Dy4eQ-MwyHFgs4abfm9JW5XcP6s_X2bpEtc8w%40mail.gmail.com

This intent message was generated by Chrome Platform Status.

[ccameron chromium]

Post-weekend ping of this CSS property.

[Mike Taylor]

Can you explain how `dynamic-range-limit: constrained-high` works with the dynamic-range media feature? Would it match standard or high (my understanding it that it's somewhere in between).

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALpoW6R%3D_hW3_xBfNGGOq4G1NV%3DeuQ-nCOD%3DeM%2BMOaPsm_dfMQ%40mail.gmail.com.

[ccameron chromium]

Correct, `constrained-high` will render content somewhere between "how it would appear on an extremely capable HDR display" (`high`) and "how it would appear on an SDR display" (`standard`). Generally, this lines up with how content would appear on a "borderline HDR" display (one that has about 1 stop of headroom).

[Mike Taylor]

Thanks for humoring me, I think my question doesn't really make much sense upon further reflection. @media(dynamic-range: standard) and @media(dynamic-range: high) are matching UA+device support, while dynamic-range-limit is telling the UA how to display elements on said device.

LGTM1

[Domenic Denicola]

On Wednesday, December 4, 2024 at 9:40:55 PM UTC+9 ccameron chromium wrote:

Contact emailsccam...@chromium.org, sboukort...@google.com

Explainerhttps://github.com/ccameron-chromium/hdr-headroom-limit/blob/main/EXPLAINER.md

Specificationhttps://drafts.csswg.org/css-color-hdr/#the-dynamic-range-limit-property

Summary

Enables a page to limit the maximum brightness of HDR content.

Blink componentBlink>CSS

TAG reviewNone

TAG review statusNot applicable

Can you explain why TAG review is not applicable to this property? I can't figure out which of https://www.chromium.org/blink/guidelines/api-owners/process-exceptions/ it might fall into.

 

Risks

Interoperability and Compatibility

None

Gecko: No signal (https://github.com/mozilla/standards-positions/issues/979)

WebKit: No signal (https://github.com/WebKit/standards-positions/issues/312) WebKit engineers have expressed positive views of this proposal (it is similar to features available on macOS and iOS).

Web developers: Positive (https://github.com/w3c/csswg-drafts/issues/9074) Adobe has endorsed this proposal. Internal developers at Google have also requested this proposal.

Other signals:

Ergonomics

None.

Activation

None.

Security

None.

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

N/A

Debuggability

None

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?Yes

Is this feature fully tested by web-platform-tests?Yes. Extensive tests of CSS properties in wpt/css/css-color-hdr.

Full end-to-end testing requires observation on an HDR display. There does not yet exist a way to test high dynamic range (or wide color gamut) rendering: https://github.com/web-platform-tests/wpt/issues/44320

Flag name on about://flagsExperimental web platform features

Finch feature nameCSSDynamicRangeLimit

Requires code in //chrome?False

Tracking bughttps://crbug.com/1470298

Availability expectationFeature available on Web Platform in browsers as they add HDR image support (only Chromium supports HDR images so far).

Adoption expectationFeature is requested by specific partners.

Non-OSS dependencies

Does the feature depend on any code or APIs outside the Chromium open source repository and its open-source dependencies to function?

No.

Sample links
https://ccameron-chromium.github.io/hdr-headroom-limit/example.html

Estimated milestonesShipping on desktop133Shipping on Android133Shipping on WebView133

Anticipated spec changesNo anticipated future spec changes.

Link to entry on the Chrome Platform Statushttps://chromestatus.com/feature/5146250411769856?gate=5206008539906048

Links to previous Intent discussionsIntent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGnfxj-m-wA4B%3Dy4eQ-MwyHFgs4abfm9JW5XcP6s_X2bpEtc8w%40mail.gmail.com

[ccameron chromium]

On Tue, Dec 10, 2024 at 3:34 AM Domenic Denicola <dom...@chromium.org> wrote:

On Wednesday, December 4, 2024 at 9:40:55 PM UTC+9 ccameron chromium wrote:

Contact emailsccam...@chromium.org, sboukort...@google.com

Explainerhttps://github.com/ccameron-chromium/hdr-headroom-limit/blob/main/EXPLAINER.md

Specificationhttps://drafts.csswg.org/css-color-hdr/#the-dynamic-range-limit-property

Summary

Enables a page to limit the maximum brightness of HDR content.

Blink componentBlink>CSS

TAG reviewNone

TAG review statusNot applicable

Can you explain why TAG review is not applicable to this property? I can't figure out which of https://www.chromium.org/blink/guidelines/api-owners/process-exceptions/ it might fall into.

Filed https://github.com/w3ctag/design-reviews/issues/1027 to go over this ("and" vs "or" in the first exception).

[Chris Harrelson]

I noticed also that there are a couple of open questions on the webkit standards review:

* Updating the spec to note the property as inherited

* Simon proposed constrained-high as a better default than high

--

You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALpoW6QCM5u5xwnjiJWOeTxourQ%2BmznPZvjq9k8sYFKp%3D8S95Q%40mail.gmail.com.

[Chris Harrelson]

LGTM2

On Wed, Dec 11, 2024 at 8:31 AM Chris Harrelson <chri...@chromium.org> wrote:

I noticed also that there are a couple of open questions on the webkit standards review:

* Updating the spec to note the property as inherited

I see this was fixed, thanks.

 

* Simon proposed constrained-high as a better default than high

I see you commented 3 weeks ago with a response to Simon that looks reasonable too jme.

[Yoav Weiss (@Shopify)]

LGTM3

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

[ccameron chromium]

Thanks all!

FYI, this has slipped to M135.

LGTM3

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.