W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2020

Re: [csswg-drafts] Revisiting standardization of the `zoom` property (#5623)

From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
Date: Thu, 15 Oct 2020 13:54:10 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-709341199-1602770048-sysbot+gh@w3.org>
> One item of particular note is that Gecko does not implement zoom (see https://bugzilla.mozilla.org/show_bug.cgi?id=390936). There are unique challenges given that authors have used a -moz-transform: scale(n) fallback in the absence of zoom. Additionally, I believe there were attempts to implement zoom in terms of transforms but that was not sufficient to alleviate compat concerns.

For reference that's https://bugzilla.mozilla.org/show_bug.cgi?id=1589766. The main idea behind that was to keep sites that used stuff like:

  zoom: 2;
  -moz-transform-origin: 0 0;
  -moz-transform: scale(2);

basically keep working. My gut feeling is that to implement `zoom` in any other way  we'd have to drop `-moz-` prefixed transforms at the same time (which is extra risk). It mostly worked, but the main issue is that stuff that used `zoom: 1` and transforms, which then resets the transform-origin and messes up, see https://bugzilla.mozilla.org/show_bug.cgi?id=1599324#c0 which is what made me turn it off.

Another quirk that you don't learn until you try that is that `zoom: 0` ends up having to mean `zoom: 1` for compat reasons... yay :/

GitHub Notification of comment by emilio
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5623#issuecomment-709341199 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 15 October 2020 13:54:12 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:20 UTC