- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Jul 2023 15:47:09 +0000
- To: public-css-archive@w3.org
Happy to discuss this further, but part of the issue with `zoom` seems pretty fundamental to me, and is that it breaks the CSS coordinate space in the page, so that CSS pixels mean different things for different elements, and basically no API accounts for that. I'm not sure what can be done to reasonably account for it? Not magically un-zooming in APIs / getComputedStyle / etc is an option, but then you cause the opposite problem, `style.width = getComputedStyle().width` not round-tripping for zoomed elements, which is also broken. For the last comment / use-case here, it seems like rather than `zoom` (which behaves like layout zoom), you'd like to expose pinch-zooming (think of the mobile phone zoom) to a subset of the page, right? Though I don't understand why `transform` or `scale` isn't that? If you need pinch-zoom behavior, an easier solution might be allowing iframes to be pinch-zoomed separately? That doesn't have the same issue `zoom` has because the coordinate space would be different across the documents. But that is probably worth a separate issue. -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5623#issuecomment-1632786085 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 July 2023 15:47:11 UTC