Here's how the browser on my desktop works.

I click on a link and immediately start reading the text on the screen.

When I click on a link in Safari, before I can read anything, I have to futz with the display resolution of the browser to make the text visible. This may not sound like a problem, but what a distraction, when following a link, before getting the idea, your mind has to take a detour into managing the device. In reading as in the movies, suspension of disbelief is broken when your mind has to exit the space of ideas and manage the projection device. It's wrong for the device to ask you this, even as a setup issue it shoudl work out of the box, but it's unacceptable that it make the user configure the browser every time it displays a new page. Today's iPhone isn't a reading device.

I thought I could overcome this by creating a special version of a site just for the iPhone that crammed all the text into a narrow column, thinking that the browser wouldn't see any need to make the text small because it would have all the necessary horizontal screen real estate to display every character at a fully visible resolution.

Nope. It still displays the text in an unreadably small font.

Here's a photo of the iPhone displaying a test page.

It's behaving like no web browser I've ever seen, and it's behaving badly. It's breaking an implicit agreement between all platforms that co-exist on the web. We create sites that assume nothing about the device they're being rendered on, and browsers should take care to make our text readable for users of their device. The iPhone web browser doesn't keep that promise.