Earlier quoted context omitted.
And with this decision you break 99% of the web on mobile devices. It's a tiny thing to override this CSS property and makes mobile browsing of desktop sites so more convenient -- there's is no difference between Chrome on a mobile device and Chrome on desktops in terms of speed and usability of sites. In contrast, using the web browser on iOS is a real pain considering that Apple forbids to install any other renderi…
> And with this decision you break 99% of the web on mobile devices. There's nothing broken about it. You can zoom in just fine; you just have to scroll back and forth, much like if you had a desktop browser opened to a tiny size. What you describe is "broken" is actually conforming to HTML and CSS spec; Android is the one that's technically "broken". Internet Explorer had a knack for creating "features" that broke s…
Personally I'm a believer in the original scheme where the site provided the content and it's largely up to the user agent to decide how to present it. This whole "Every rendering engine should create the exact same rendering of the page down to the pixel" is super useful for web apps and stuff, but most of the time I just want to read stuff. Honestly, I'm surprised there's no web browser that just runs the Readable scriptlet on any page that looks like an article by default.