The link to the specification: https://github.com/w3c/csswg-drafts/pull/9699 list behaviors and then says
> Web compat analysis: the above is what is already implemented in WebKit and Chromium browsers.... But one of the behaviors listed is > devicePixelRatio is affected by zoom inherited from an ancestor frame devicePixelRatio never changes in WebKit. On Fri, Feb 2, 2024 at 11:18 AM 'Yotam Hacohen' via blink-dev < blink-dev@chromium.org> wrote: > Contact emailsyo...@google.com > > ExplainerNone > > Specificationhttps://github.com/w3c/csswg-drafts/pull/9699 > > Design docs > https://docs.google.com/document/d/1AcnDShjT-kEuRaMchZPm5uaIgNZ4OiYtM4JI9qiV8Po/edit > > Summary > > Aligns the existing implementation of the previously non-standard CSS zoom > property to align with the new standard. This changes various JS APIs to > align with the spec (see design doc), change zoom to apply to iframes, and > change it to apply to all inherit all length properties (currently it only > changes inherited font-size) > > Blink componentBlink>Paint > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EPaint> > > TAG reviewNone > > TAG review statusPending > > Risks > > Interoperability and Compatibility > > There is web compatibility risk for these changes. However, previous > research indicates broken content due to unexpected changes of the JS APIs > is very unlikely, since: * The changes to the JS API simply change the > coordinate space of the responses, not the syntax or what APIs are > available. * Most pages found during the research didn't appear to use CSS > zoom at all and the ones that did only relied on the visual effect, not JS > APIs. It's possible some pages will be broken by the changes to inherited > properties other than font-size, or applying zoom to sub-frames, but based > on previous research, those are very likely to be minor visual changes that > don't break fundamental user interaction with the site. None of the sites > reviewed contained iframes underneath a zoomed ancestor. We will use direct > outreach to avoid any broken features in Office 365 or the Gmail native > mobile app > > > *Gecko*: No signal Filed a standard position request: > https://github.com/mozilla/standards-positions/issues/977 > > *WebKit*: No signal Filed a standard position request: > https://github.com/WebKit/standards-positions/issues/311 > > *Web developers*: Positive ( > https://docs.google.com/document/d/1cmbXpjAcXAht2ufi7bNKy-rbVNveqaf0UzeYg_DIMNA/edit#heading=h.6sz4u73bikbd) > Research collected as part of the previous attempt to remove CSS zoom > demonstrated several use cases. > > *Other signals*: > > WebView application risks > > See Interoperability and Compatibility above > > > Debuggability > > None > > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, ChromeOS, Android, and Android WebView)?No > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ?Yes > > All JS APIs affected by zoom are tested with the following wpt tests: > https://wpt.fyi/results/css/cssom-view/offsetTop-offsetLeft-with-zoom.html?label=master&label=experimental&aligned&q=cssom-view%2FoffsetTop-offsetLeft-with-zoom.html > https://wpt.fyi/results/css/cssom-view/client-props-zoom.html?label=master&label=experimental&aligned > https://wpt.fyi/results/css/cssom-view/getBoundingClientRect-zoom.html?label=master&label=experimental&aligned > https://wpt.fyi/results/css/cssom-view/getClientRects-zoom.html?label=master&label=experimental&aligned > https://wpt.fyi/results/css/cssom-view/scroll-zoom.html?label=master&label=experimental&aligned > https://wpt.fyi/results/intersection-observer/zoom-scaled-target.html?label=experimental&label=master&aligned > > Flag name on chrome://flagsStandardizedBrowserZoom > > Finch feature nameStandardizedBrowserZoom > > Requires code in //chrome?False > > Sample linkshttps://jsbin.com/wasafateko/edit?html,css,js,output > > Estimated milestones > > No milestones specified > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5198254868529152 > > 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/CAAOtuiYKjC9Gt%2BgXwWNT_hJneBMa053RizCX5Xj5p_07CVLXkA%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAOtuiYKjC9Gt%2BgXwWNT_hJneBMa053RizCX5Xj5p_07CVLXkA%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/CAKZ%2BBNoHUokrgx%3Dp%3DgT%2BBv_aA4srJcYY6n8nWbpKPyydWmfNDw%40mail.gmail.com.
