On Fri, Apr 14, 2023 at 5:09 PM PhistucK <phist...@gmail.com> wrote:
> Any alternatives? I thought there was a section in the intent templates > for that... > One alternative for the use case mentioned in my earlier email is to apply a CSS transform instead. This will magnify the subtree visually but not cause a zoom-style layout change. Another alternative is for the developer to multiply the numbers in their CSS properties via calc + variables. > > ☆*PhistucK* > > > On Sat, Apr 15, 2023 at 1:03 AM Chris Harrelson <chris...@chromium.org> > wrote: > >> Contact emailschris...@chromium.org >> >> Specificationhttps://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 componentBlink>CSS >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS> >> >> TAG reviewNone >> >> TAG review statusNot 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# >> >> *Gecko*: Shipped/Shipping (Firefox never supported the feature.) >> >> *WebKit*: No signal ( >> https://github.com/WebKit/standards-positions/issues/170) >> >> *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 nameCSSZoom >> >> 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/CABc02_%2Br8k-q-bKWGFKxgNbSy97UKGf7VUSMnrnURBJHor-x_w%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABc02_%2Br8k-q-bKWGFKxgNbSy97UKGf7VUSMnrnURBJHor-x_w%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/CAOMQ%2Bw_yfVCi3aWq7X%3DhW%2BTUrPpdOZ7-L2bBxhHfQ9f%3DuRGObA%40mail.gmail.com.
