- From: jwdevel via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Sep 2024 21:12:03 +0000
- To: public-css-archive@w3.org
> ... the whole point to me would be that it doesn't matter _why_ a viewport is reported as being a particular size, as a developer you should design your content so it works well within your given viewport (regardless of what _actually_ caused it to be that way). I just want to give my 2¢ as a random developer: I do feel like being able to distinguish between these cases is useful — I'll give an example. I have a "card" style layout on a page, where each card is a rectangle, and they get arranged on a grid. All the cards to have a common height, so they look nice next to each other, fitting on that grid. On smaller devices (eg: a tablet vs a wide desktop window), I want to shrink the card size a little bit, so the user still sees approximately the same number at a time. So, the card height is shrunk, via `@media` query. This also requires the font to shrink, so it doesn't spill out, but let's even ignore that and just talk about the boxes themselves. When looking at the site across several devices, everything looks good. However, when a desktop user views the site, and presses "Ctrl+", they get the jarring experience that the cards become *smaller*. This is a bad experience, and I want to avoid it. A user pressing "Ctrl+" expects the stuff onscreen to get bigger, generally speaking. Right now, I have no way (that I know of) to distinguish between the case where I want to shrink (for a tablet or phone) and the case where I do *not* want to shrink (due to Ctrl+). For me, the key differentiator is that "Ctrl+" indicates a certain *intent* by the user that they want things to get bigger. So, I want to deliver on that expectation. On the other hand, a user on a smaller device visiting the site for the first time just wants to see the best-laid-out version of the site for them. They did not express any intent for zooming. Thus, being able to distinguish between these cases allows me to make decisions that better please my users. Hopefully that makes sense. I realize this thread is about font sizes, and specifically referencing WCAG guidelines, but this is a generally-useful feature, in my opinion. -- GitHub Notification of comment by jwdevel Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6869#issuecomment-2344711025 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 September 2024 21:12:04 UTC