Category: Web Browsers

Posted on
by

Q: What happens when you break up/fire your web browser-developing group with years of experience, and later hire an outside firm to build your next product?

A: Netscape 8.

IEBlog has an amazing report—which I’ve just verified. Netscape 8.0.1 disables IE’s XML rendering. So if you try to load an XML document—say, an XSLT-styled RSS feed like the feed for this blog—using Internet Explorer or Netscape 8 with IE’s engine, you’ll see either a blank page or an unloaded-image icon.

Apparently every time Netscape 8 runs, it trashes a registry entry that defines how IE displays XML. At this point the only way to fix it is to uninstall Netscape 8 and delete that entry (directions at the above link).

This raises two questions:

  1. Why does Netscape 8 alter an Internet Explorer registry setting?
  2. Why can Netscape 8 alter an Internet Explorer registry setting?

I’ve said it before (though possibly not here), but Mozilla is much better off now that AOL isn’t calling the shots.

Update June 20: Netscape 8.0.2 fixes this problem.

Posted on
by

Opera BrowserThere’s a saying about the elephant in the room that no one will talk about. Everyone knows it’s there, but by some unspoken rule no one will mention it. I’ve noticed that when web browsers are compared, there’s one thing Opera supporters tend to ignore or downplay: Opera’s business model.

Internet Explorer and Safari are bundled with their respective operating systems, and so they’re perceived as free. Firefox is free in both the gratis and libre senses of the word. Opera, however, is ad-supported by default and will disable the ads if you pay for it.

You can use Opera without paying money, but you’re still paying it in attention (a persistent chunk of space dedicated to advertising), so in comparison to the other three leading browsers, it’s perceived as being less free. Think of it in terms of television.

So the perception of cost looks like this:

  • IE, Safari, Firefox (commercial-free TV)
  • Ad-supported Opera (network TV)
  • Paid-for Opera (cable or satellite)

Most people really do prefer free without ads to free with ads or paid subscriptions. Why else is skipping commercials one of Tivo’s most popular features?

I’m certain this impacts marketshare, and it definitely impacts media coverage. Just look at CNET’s recent IE vs. the world review. Opera 8 gets high marks for features, but what’s the summary? “Despite a ton of great technology in Opera, few consumers will be likely to pay for the app. ” Whether you think the review is otherwise fair or not, the business model clearly lowered it several notches on the reviewer’s scale.

Next: Firefox’s blind spot.

Disclaimer: I’m a regular Firefox user these days, but I’ve also paid to register Opera since version 3.5 was current back in 1999. I used Opera as my main web browser on Windows back when Netscape 4 was aging and Mozilla hadn’t yet stabilized enough to replace it.

Posted on
by

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 →

Posted on
by

Opera BrowserSorry for the misleading title, it’s sort of an homage to CNET’s recent coverage of Firefox.*

Opera CEO Jon von Tetzchner, excited by the response to Opera 8.0, promised to swim from Norway to the US if Opera 8.0 managed 1 million downloads in 4 days. (By comparison, Firefox 1.0 managed 1 million in less than a day, and hit 2.5 million by the end of day 2.

Well, they did it, and von Tetzchner has donned a wet suit.

Tetzchner entered the “freezing Oslo fjord” on Monday and started swimming toward the United States, the company said. Opera’s public relations manager, Eskil Sivertsen, is rowing an inflatable boat alongside Tetzchner “as an act of guilt after making the CEO’s statement public,” according to the Opera Web site.

Full details, photos, and a map are at Opera.com/swim. [archive.org]

Update two days later:

Let me tell you, those PR folks at Opera know how to set up a publicity stunt.

In a “dramatic” update to the saga, Opera’s CEO won’t finish swimming to America after all, as his PR manager’s raft deflated an hour into the day’s swim.

Some choice quotes:

“As much as I don’t want to talk behind a colleague’s back, there is no doubt that we would never have let Eskil assist Jon in the raft had we known he can neither swim nor read maps,” says an embarrassed Tor Odland, Opera’s Communications Director. “I feel partly responsible for letting Jon down, as he cannot possibly continue without the raft.” [emphasis added]

A local farmer spotted the drama from his kitchen window and took surprisingly sharp photos with a remarkably powerful telescopic lens.

“And my mother [in Iceland] will be so disappointed when I call and tell her that I won’t be stopping by for hot chocolate after all.”

The tongue-in-cheek tone of the whole thing is right up there with the Opera Bork Edition that translated the MSN website into the Swedish Chef’s unique form of gibberish. That was to point out the ridiculousness of MSN singling out visitors using Opera and sending them a broken—or perhaps we should say borken—page.

It’s kind of funny how Opera can get away with stunts like this. Microsoft or Apple would be embarrassed to even consider it, and Mozilla wouldn’t dare. These days Mozilla/Firefox is too busy fighting uphill for respect. They wouldn’t risk sanctioning the “Always use Protection” poster, and they wouldn’t try something this wacky. Whatever happened to the days when the IE team deposited a big blue “e” on Netscape’s front lawn?

—

*Things like “Mozilla flaws could allow attacks, data access” which didn’t just bury but actually omitted the fact that a fixed version had been released three days earlier, and that the disclosure was made as part of the release. The second-to-last sentence, “All versions of Mozilla Suite prior to version 1.7.7 and all versions of Firefox prior to 1.0.3 are vulnerable.” sort of hints at it, if you know that these are the newest versions, and if you don’t misread it as “through” instead of “prior to.” And the original article on the Opera swim promise misstated the Firefox download numbers using one of the preview releases instead of the big launch, claiming it took 5 days to reach 1 million. They’ve “corrected” it to “within days,” which is technically true—but wouldn’t “in less than a day” be more accurate and better convey the contrast? Compare this to other articles from last week like “Apple patches iSync flaw” and “RealNetworks fixes ‘highly critical’ flaw” and you have to wonder whether there’s a misinformation campaign some editorial bias involved.

Posted on
by

Sometimes you want to know exactly what software people (or bots) are using to view your website. Sometimes all you want to know is which rendering engine’s quirks you need to cater to. To that end, I have here the ultra-simple browser detection algorithm. Just check the User-Agent string for each of the following words, in order:

  1. Opera — they spoof IE by default, so check here first. If they ever change this to something else, you’ll be glad you started here.
  2. KHTML — this will catch Safari, Omniweb and Konqueror. They mention Gecko, so if you need to treat them differently, check for KHTML first.
  3. Gecko — this will catch Mozilla, Firefox, Camino, Netscape 6+, etc.
  4. MSIE — this should Internet Explorer and anything else that uses its engine.
  5. bot, spider, crawler, or compatible — filter out robots and anything unknown.
  6. Mozilla — just about everyone uses Mozilla in their UA string these days, but the rules above should filter most of them out and leave only old-school Netscape.

Of course, Mozilla, Opera and Safari have put much more effort than IE into following the standards, so most of the time you can write your code using the spec and just build in work-arounds. The way I look at it, there are three main categories:

  1. Standards-compliant(ish) browsers: Gecko, Opera, KHTML
  2. MSIE
  3. Everything else

I write for group 1, work-around for group 2 (and sometimes other browsers in group 1), and figure that group 3 (with the exception of Netscape 4, which has a tendency to do things like make links unclickable or hide entire chunks of the page if it doesn’t like your CSS) should at least be able to figure out how the text and graphics break down. It may not look perfect in randombrowser, but it should at least be comprehensible.