- From: Mason Freed via GitHub <sysbot+gh@w3.org>
- Date: Thu, 24 Aug 2023 22:07:42 +0000
- To: public-css-archive@w3.org
> What if only one dimension of the screen is small, but the other is big? Yeah, that's a good question. Mostly people use the width as a proxy, but again here, this might be a great reason to let the UA define it? That device doesn't exist (or isn't common today) so it's impossible to get it 100% right without knowing how it's used. The alternative of hard-coding a specific width seems worse in this case, doesn't it? > Also, I'm not convinced by the argument for not defining them. What will happen is that authors will rely on whatever Blink chooses, and Blink will be locked into that initial choice to avoid breaking sites. I agree that would be a bad outcome. How do you propose we define it to avoid this problem? My hope was that by *not* defining it in terms of pixels, developers would use it more for the qualitative breakpoints, such as "more padding", or "add a backdrop". Perhaps browser devtools can randomize the breakpoint, so developers can't count on a width while developing? I'm open to suggestions. -- GitHub Notification of comment by mfreed7 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7696#issuecomment-1692477888 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 24 August 2023 22:07:45 UTC