And then Google built Chrome, and Chrome used Webkit, and it was like Safari, and wanted pages built for Safari, and so pretended to be Safari. And thus Chrome used WebKit, and pretended to be Safari, and WebKit pretended to be KHTML, and KHTML pretended to be Gecko, and all browsers pretended to be Mozilla, and Chrome called itself Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.2.149.27 Safari/525.13, and the user agent string was a complete mess, and near useless, and everyone pretended to be everyone else, and confusion abounded.

via Daring Fireball

Very good…

Was round the in-laws the other day and couldn’t help but notice this one in the garden…

A fine way to retire an old web browser. At least it’s found some use…

We’ve decided that IE8 will, by default, interpret web content in the most standards compliant way it can. This decision is a change from what we’ve posted previously.

read more

Microsoft has sent out invitations to a select number of testers allowing them to participate in a “limited technical beta program” for the upcoming Internet Explorer 8. The announcement also says that there will be a public beta as well, once the invitation version is complete.

So far we know that Microsoft claims that IE 8 will pass the ACID 2 compatibility test and include support for a controversial “version tag,” which will allow web developers to force the browser into “super-standards” mode — enabling the browser to correctly render webpages that adhere to the W3C’s standards.

We’ve written before about the contentious debate surrounding the so-called version tag, but the basic idea is that website developers will be able to add a meta tag to their pages telling IE how it should render the page — in traditional mode (non-standard IE 6-style rendering), standards mode (IE 7’s half-baked concept of standards) and super standards mode (where IE will render similar to the way Firefox, Opera and Safari have been doing for the last five years).

A number of developers have decried the meta-tag flagging as a way of versioning the web, which they feel is a bad idea. But regardless of how the meta-tag might play out, we find it interesting that, if the rumors are to be believed, IE 8 will automatically render in traditional mode.

full story

In the area of web browsers, Opera Software has proposed a specific kind of remedy - that Microsoft only be allowed to distribute standards-compliant browsers. Microsoft’s IE is bug-ridden and the company, despite its vast resources, has shown little interest in fixing problems that cost web designers time and sleep. IE dominates the web due to its being bundled with Windows. This forces web designers to prioritize coding for IE. Coding for standards-compliant browsers becomes a secondary consideration.

Microsoft is keenly aware of this and therefore has little interest in improving their support for standards. They will never become standards compliant unless forced by someone in a position to demand a change, something that users and customers are not. Requiring standard compliance would greatly lessen Microsoft’s monopolistic stranglehold in the web browser market, would delight web developers everywhere and would, ironically, make IE a better product.

He’s a fan of Microsoft’s latest proposals in conjunction with IE8…

via

via

via