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

On 12/9/24 10:30 PM, ccameron chromium wrote:
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 <https://drafts.csswg.org/css-color-hdr/#introducing-headroom>).

On Mon, Dec 9, 2024 at 2:10 PM Mike Taylor <miketa...@chromium.org> wrote:

    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).

    On 12/9/24 6:25 PM, ccameron chromium wrote:
    Post-weekend ping of this CSS property.

    On Wed, Dec 4, 2024 at 1:40 PM ccameron chromium
    <ccame...@chromium.org> wrote:


                Contact emails

        ccame...@chromium.org, sbouko...@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
        
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS>


                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
                
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?

        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
        <https://chromestatus.com/>.

-- 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+unsubscr...@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
    
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALpoW6R%3D_hW3_xBfNGGOq4G1NV%3DeuQ-nCOD%3DeM%2BMOaPsm_dfMQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.


--
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+unsubscr...@chromium.org.
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ad01b00f-ca35-43e0-97aa-e35bc35cc744%40chromium.org.

Reply via email to