So who’s next? Well, Opera 9 beta 1 is very close—there’s a pair of red squares that should be black, but that’s it. Neither IE7 nor Firefox 1.5 will have much in the way of Acid2-related fixes, though the trunk builds of Firefox show improvement, so 2.0 has a chance 3.0 might make it will pass (since 2.0 will use the same engine as 1.5).

Safari LogoA few days ago I noticed that while Safari accounts for about 2.3% of traffic to this site, Mac OS accounts for 4.4%. Since Safari only runs on Mac OS X, that means that just over half of Mac users visiting this site* are using Safari.

I realized that the detail page pulls out Mac OS X, which makes up 2.8%…but MSIE doesn’t say whether it’s running on Classic or OS X. Fortunately IE 5.2 is OS X-only, so we can add in that 0.6%, leaving us with an estimated 3.4% on OS X and 1% on Classic.

So, to the extent that these stats are reliable…

  • Nearly one fourth of Mac users visiting this site are still running an obsolete version of the OS.
  • 65% of Mac OS X users are using Safari, with only 20% on Internet Explorer.

Anything more detailed is going to require going through the logs myself or writing my own stats script, so I have no idea how the remaining 15% breaks down.

*All of hyperborea.org.

On Sunday, a development version of Konqueror passed the Acid2 test. In the comments, someone posted a screenshot of iCab also passing the Acid2 test.

I did a double-take. iCab? Das Internet-Taxi für den Mac? The browser with the nice “Make iCab smile” campaign to encourage non-broken HTML on websites but CSS capabilities that have rivaled Netscape 4 as little better than a bad joke? That has been in perpetual beta for years with no sign of shipping a final release?

So I did the only thing I could do. I downloaded the new beta and tried it. Not only did it nearly pass Acid2 (there was a narrow white line across the middle of the face) but it actually handled all the layouts on my own site… something which it had always failed at spectacularly before.

The WaSP Buzz posted a congratulatory note to both this morning. Strangely, iCab is the first browser available to the general public that passes Acid2. The up-to-date Safari is still sitting inside Apple’s development labs, and while you can download the source for the updated Konqueror, you’ll have to wait for KDE 3.4.2—or possibly 3.5—to be able to use it yourself without running a bleeding-edge desktop. Update: Apple has just launched CVS access to WebCore, putting Safari in the same situation as Konqueror: you can download and compile the latest source code if you want, but if you just want to grab an installer, you’re gonna have to wait.

Some potentially nasty browser security vulnerabilities found this weekend in Mozilla and in Safari. Both involve software update mechanisms. The Firefox one tricks the browser into thinking it’s installing from a trusted update site (the maintainers of updates.mozilla.org and addons.mozilla.org—the only trusted sites by default—have made some changes on their server to prevent the exploit from working). The Safari one takes advantage of the Macintosh tradition of automatically opening archives. This one just happens to unzip itself into the location where Dashboard stores its widgets.

IEBlog has weighed in with a balanced (i.e. non-fanboyish) comment on just who “us” vs. “them” should mean: responsible developers & security researchers vs. the malicious ones. It won’t happen—people are too hunkered down in their own trenches—and even with Mozilla, Opera and Apple collaborating on specs, I don’t expect to see much in the way of collaboration on security except in the actual open-source world. (Even then, I suspect there’s too much rivalry between Gecko and KHTML developers to do much collaboration.) Continue reading

It’s been anticipated since Apple first announced Safari, but it’s still a minor shock to see it actually happen. Daring Fireball reports that Internet Explorer is no longer included with Mac OS X Tiger.

You can still download it from Microsoft, but given that they dissolved the development team a few years ago, there’s not much point except for site testing.

(The one I can’t figure out is why they’ve apparently left out StuffIt Expander as well.)