You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 10, 2022. It is now read-only.
"In order to attempt to provide the best experience, mobile browsers will render the page at a desktop screen width (usually about 960px), "...
Actually, it's exactly 980px on just about every smartphone with a WebKit based browser (aka most of them), and 1024px on IE mobile and Blackberry. See http://www.quirksmode.org/mobile/metaviewport/
iPhone
iPad
Android Samsung
Android HTC
Chrome
Opera Presto
Kindle Fire
BlackBerry
IE
980
980
980
980
980
980
980
1024
1024
It's a small, but important detail.
The text was updated successfully, but these errors were encountered:
I always say 800-1024px. Old Androids may use anything from 800 to 1000. 1024 seems to be the maximum right now. And we shouldn't encourage people to focus on just one resolution, so a range would be best. I think.
I'm in violent agreement about encouraging developers to do the right thing, but I think being purposefully misleading isn't a great idea either. I think a range would be fine, but if you're going to keep "about" I would encourage you to use 980px as that's definitely the most common resolution devs will encounter today.
Ah well, it doesn't really matter a lot. It's just that I've spent the last weeks writing book chapters about all these topics, so I have now My Way of Explaining It. And everybody else's is Wrong.
In rwd-fundamentals the paragraph reads:
"In order to attempt to provide the best experience, mobile browsers will render the page at a desktop screen width (usually about 960px), "...
Actually, it's exactly 980px on just about every smartphone with a WebKit based browser (aka most of them), and 1024px on IE mobile and Blackberry. See http://www.quirksmode.org/mobile/metaviewport/
It's a small, but important detail.
The text was updated successfully, but these errors were encountered: