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

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

From: Daniel Libby via GitHub <sysbot+gh@w3.org>
Date: Fri, 16 Oct 2020 20:33:46 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-710579718-1602880425-sysbot+gh@w3.org>
Thanks for those pointers! Sounds like there are two core objections:
1. Specifying the current behavior may be difficult and could very well end up codifying some really strange behavior if there are no appetite for implementation changes due to compat concerns.
1. Shipping this in Gecko has increased risk due to the probably need to sim-ship deprecation of -moz-transform.

I did go through crbug to see I could pull out a signal of the breadth of issues and tagged the ones that I found (searched "css zoom" and skimmed the titles, so probably not exhaustive):
https://bugs.chromium.org/p/chromium/issues/list?q=label%3Acss-zoom&can=1

I did a similar exercise in WebKit's bugzilla but did not discover anything unique (though again I could have missed something).

Certainly the `getBoundingClientRect()` behavior stands out as particularly weird and difficult to justify the standardization of such strange behavior. I'm not entirely sure the rest would be insurmountable to document/reconcile, and as you mention there is probably other weirdness to find when digging in further.

In any case, I think this is worth having a broader discussion to get consensus on next steps, so tagging for TPAC. 

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 October 2020 20:33:48 UTC

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