On Sat, Apr 15, 2023 at 6:29 PM Mike Taylor <miketa...@chromium.org> wrote:
> > On 4/14/23 8:03 PM, Chris Harrelson wrote: > > Contact emails chris...@chromium.org > > Specification https://developer.mozilla.org/en-US/docs/Web/CSS/zoom > > Summary > > Removes support for the non-standard "zoom" CSS property. This CSS > property causes computed lengths for an element to be multiplied by the > specified zoom factor. > > > 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 > > This feature is only available in Webkit and Blink-based browsers, and has > been present in Chrome since the beginning. Usage is a little above 0.5% of > page loads: > https://chromestatus.com/metrics/feature/timeline/popularity/3578 > However, research shows that sites in HTTPArchive triggering the feature > mostly don't even seem to use it, and those that do appear to always use it > in a way that works fine without zoom applied - worst case, just a very > minor change to the size of a tiny number of UI elements, but the UX is > basically the same. See: > https://docs.google.com/document/d/1cmbXpjAcXAht2ufi7bNKy-rbVNveqaf0UzeYg_DIMNA/edit# > > It would also be good to go through all duplicates and "See Also" bugs > linked at https://bugzilla.mozilla.org/show_bug.cgi?id=390936 and see how > we fare with a build that has zoom disabled. > Is it possible to also expose the usecounter as UKM, and see the usage distribution? Given the high usage percentage, it can be reassuring to see that a) No large sites get broken by this b) Long tail sampling from UKM matches what y'all saw in HA > *Gecko*: Shipped/Shipping (Firefox never supported the feature.) > > *WebKit*: No signal ( > https://github.com/WebKit/standards-positions/issues/170) > > https://github.com/WebKit/standards-positions/issues/170#issuecomment-1509480131 makes an interesting point that things could break when users actively zoom-in the page. > > *Web developers*: Some web developers like the feature, in particular for > the use case of zooming in content in a legible way with responsive design. > See comments regarding that in this issue; > https://github.com/w3c/csswg-drafts/issues/5623 > > *Other signals*: The CSSWG has decided to not specify this feature: > https://github.com/w3c/csswg-drafts/issues/5623 > > Ergonomics > > See "other views" section. > > > Activation > > N/A > > > 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? > > Maybe. WebView-based apps might use this feature. > > > Debuggability > > Sites should be able to see that zoom no longer applies to elements in > devtools, though there is no warning planned. > > > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, 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> > ? No > > Flag name CSSZoom > > Requires code in //chrome? False > > Sample links > https://output.jsbin.com/yimuwax > > Estimated milestones > Shipping on desktop 114 > DevTrial on desktop 114 > Shipping on Android 114 > DevTrial on Android 114 > Shipping on WebView 114 > > Anticipated spec changes > > Open questions about a feature may be a source of future web compat or > interop issues. Please list open issues (e.g. links to known github issues > in the project for the feature specification) whose resolution may > introduce web compat/interop risk (e.g., changing to naming or structure of > the API in a non-backward-compatible way). > None > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/6535859207143424 > > Links to previous Intent discussions > > 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/CAOMQ%2Bw_2izF%2BTzHvALsKSxD_uLds%2BPAD7fLtvpX4Cwe7sTwU7g%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_2izF%2BTzHvALsKSxD_uLds%2BPAD7fLtvpX4Cwe7sTwU7g%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/745a0332-2bdf-5d77-e05d-56722211ffc1%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/745a0332-2bdf-5d77-e05d-56722211ffc1%40chromium.org?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/CAL5BFfV70dHxzFOP6Xxe%3DwMsr9TSYOxzv0QnAbY6cCLTw4nS8Q%40mail.gmail.com.
