- From: James Craig via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Dec 2021 00:12:11 +0000
- To: public-css-archive@w3.org
Thanks for your patience in the explanation. I wrote: > > Typically when low viz users zoom in, they expect the content to stay the same, not adjust with the zoom ratio. @scottkellum replied > Maybe I’m misunderstanding you here but isn’t this expectation the opposite of what happens currently with browser zooming? There are a bunch of different types of "zoom." In native AT zoom, and web viewport pinch-to-zoom, also iOS's double-tap viewport zoom to text column, the user presumably does not want the layout to change at all. Your example of keyboard-hotkey-based zoom is has a discrete number of levels, so I'll refer to this as "discrete" zoom since I'm not aware of an official name. As others noted above, Safari also has a "text-only" zoom that also has discrete incremental steps, but I don't believe that type of zoom is necessary to discuss further in this context. There may be 5th or 6th type of zoom I'm not recalling. In regards to the primary discrete zoom, I read two concerns... One of them is that the layout breaks in current release at large zoom levels, but I think (?) the linked example could be salvaged by adding an em-based min-width to the main layout container... The second (probably the primary issue) viewable in Chrome Canary may be that the hierarchy changes as the [discrete] zoom level increases, such the difference between these two screen shots, only one zoom level apart. | Lower Zoom | Next Higher Zoom Level | | --- | --- | | ![second level hierarchy preserved, but text slightly smaller](https://user-images.githubusercontent.com/75867/145907837-9c8d9831-7c14-4b00-afae-6586b608c75a.png) | ![second level hierarchy lost, but text slightly larger](https://user-images.githubusercontent.com/75867/145907941-908283ab-428c-4c3c-8b05-bf689cb67b94.png) | Before responding further, does that capture the concern, or am I still off the mark? Thanks. -- GitHub Notification of comment by cookiecrook Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6869#issuecomment-993026788 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 14 December 2021 00:12:13 UTC