On 3/1/23 3:41 PM, Domenic Denicola wrote:


On Wed, Mar 1, 2023 at 10:14 PM Yoav Weiss <yoavwe...@chromium.org> wrote:



    On Tue, Feb 28, 2023 at 4:07 PM Daniil Sakhapov
    <sakha...@chromium.org> wrote:

        agree, my mistake, I thought about explaining 3 types of
        output displays, not the media feature values

        On Tue, Feb 28, 2023 at 2:28 PM Patrick Lauke
        <splinte...@gmail.com> wrote:

            Shouldn't the first value be `none` rather than `print` ?

            On Tuesday, 28 February 2023 at 12:22:03 UTC Daniil
            Sakhapov wrote:


                        Contact emails

                sakh...@chromium.org


                        Specification

                https://drafts.csswg.org/mediaqueries-4/#descdef-media-update


    This is one of the rare cases where the feature is simple enough
    and the spec is clear enough that an explainer is not really
    needed! :)



                        Summary

                Implements "update" media feature. Allows to
                distinguish styles for print, slow and fast output
                displays: print - for documents on the paper; slow -
                for e-ink and underpowered displays; fast - regular
                computer displays.

                Note:

                Browser should set the web setting, saying if it has a
                slow or fast screen, default is fast.


                        Blink component

                Blink>CSS
                
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS>


                        Risks


                        Interoperability and Compatibility


                /Gecko/: Shipped/Shipping


    (You could have used the WPT results
    
<https://wpt.fyi/results/css/mediaqueries/update-media-feature.html?label=master&label=experimental&aligned>
    as a link to back this up)


                /WebKit/: No signal


    Can you file a WebKit position?


I wonder if this might not be necessary for features that are part of Interop 2023? I think given the veto process in how that list is assembled, that guarantees at least a "neutral" position from all vendors. (Knowing whether WebKit feels "positive" or "neutral" about the feature might be interesting, but doesn't feel like a great use of our or their time, at least for small features like this.)

I like this idea, but let's move this part of the discussion to blink-api-owners-discuss@ (I can start a thread), and we can circle back with an update on the consensus view.



    Any word on web developer demand for it?


                /Spec/: the feature is marked as "at risk", but it's
                part of the Interopt 2023 + Firefox has shipped it. We
                can save the feature!



                        Is this feature fully tested by
                        web-platform-tests
                        
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?

                Yes
                https://wpt.fyi/css/mediaqueries/update-media-feature.html


                        Flag name

                CSSUpdateMediaFeature


                        Tracking bug

                https://bugs.chromium.org/p/chromium/issues/detail?id=791028


                        Estimated milestones

                DevTrial on desktop     113

                DevTrial on Android     113


                        Link to entry on the Chrome Platform Status

                https://chromestatus.com/feature/5154424982339584

                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 on the web visit
        
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAH3Z92_-FaTz7z9S-eiWGw-_ZOap32FcOVig3VMJLxguQpoq0Q%40mail.gmail.com
        
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAH3Z92_-FaTz7z9S-eiWGw-_ZOap32FcOVig3VMJLxguQpoq0Q%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 on the web visit
    
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfXj2fq55euPxrtoGuCAer7%3D6qUgKZZgZqwEp6_neRYAcg%40mail.gmail.com
    
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfXj2fq55euPxrtoGuCAer7%3D6qUgKZZgZqwEp6_neRYAcg%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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM0wra8%3Ds5d3wb%3DsQP2OcNHaiVw-rDR6pm0x5yOEr6et8R_z6A%40mail.gmail.com <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM0wra8%3Ds5d3wb%3DsQP2OcNHaiVw-rDR6pm0x5yOEr6et8R_z6A%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 on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/c7bec13d-3bc6-f210-b4ce-a1b8f3bbfdbb%40chromium.org.

Reply via email to