4 ms·
I'm not an expert. But in my experience, that line has been the solution to 100% of any viewport issue I've ever had on mobile, and has made webpages "just work
by akersten 7y ago
I'm not an expert. But in my experience, that line has been the solution to 100% of any viewport issue I've ever had on mobile, and has made webpages "just work" and render how I'd expect them to on mobile, as opposed to weird issues with font size and scrolling.
I've never had that line do something I didn't want. Is there a reason mobile browsers don't automatically just do whatever that line does? Seems like the opt-in behavior should be "yes, render me like I'm a desktop site on a tiny monitor" rather than opt-out.
- Brendinooo 7y agoLegacy reasons. When the iPhone came out, "mobile only" sites were a wasteland of terrible UI and restricted features. iPhone OS wanted to serve full websites, and sometimes had to do weird things to beat the kind of stuff that sniffed for mobile devices, or to overcome the lack of a mouse on a desktop website. If you look at the original iPhone demo in 2007[0], the original intent was to render full web pages on the screen and rely on the double-tap-to-zoom to read content. The article that's generally credited with naming and mainstreaming Responsive Web Design[1] didn't come until 2010. [0]: https://youtu.be/vN4U5FqrOdQ?t=2502 https://youtu.be/vN4U5FqrOdQ?t=2502 [1]: https://alistapart.com/article/responsive-web-design/ https://alistapart.com/article/responsive-web-design/
- maccard 7y agoCompletely off topic, but it's hilarious how slow the NY times website loads in that first video.