Category: Web Browsers

Posted on
by

The new Opera 8.0.1 includes an experimental feature called Browser JavaScript. It’s a collection of client-side scripts that automatically corrects known errors on websites as they’re displayed. Opera downloads updated scripts once a week.

It’s an extension of the User JavaScript concept. Firefox’s Greasemonkey is basically the same thing, and it’s gotten a lot of attention as a method for correcting or enhancing sites. The key difference is that these scripts are centrally maintained, and automatically updated.

Browser JavaScript is disabled by default, and can be turned on by putting Browser JavaScript=1 in the [User Prefs] section of your opera6.ini file.

(via Opera Watch)

Posted on
by

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.

Follow-up in 2024: I’m surprised to discover that iCab still exists, and is still developed — though in 2020 the author rewrote it so it uses macOS’ built-in web renderer (like Safari) and not its own engine anymore.

Posted on
by

FirefoxFollowing up on my comments on Opera, Firefox supporters have a major blind spot as well. It has to do largely with the heavy emphasis on web standards among the developers and the early adopters, and the ideals of the open source/free software community. There are a lot of websites out there that don’t look quite right on anything but Internet Explorer, and there are sites out there that just plain don’t work in anything but IE. This is largely due to three facts:

  • There is a lot of broken HTML out there that has only been tested on IE, and the designers relied on IE’s particular error-recovery behavior.
  • There are sites that rely on ActiveX or other IE-specific code without providing an alternative.
  • There are sites with bad browser-detection logic that deliberately exclude other browsers, regardless of whether they would otherwise handle the site.

In each case you can either change the browser to handle the websites, or you can change the web to handle the browser. Both approaches are difficult, and while the former often yields more immediate results, the latter is more ideal, because it benefits users of all web browsers. In most cases Opera has chosen to adapt the browser, while Mozilla has chosen to promote standards for web development. Continue reading →

Posted on
by

Browse HappyI didn’t see that one coming:

BrowseHappy Now Part of WordPress as WaSP Refocuses Mission.

Apparently the Web Standards Project decided they’d be better off remaining neutral. So they’ve handed it off to WordPress, who has been promoting Firefox on their website and in the admin interface for months.

It’s an odd fit, but who knows? Maybe the new management will be insterested in adding some more varied testimonials (they’re almost all Firefox right now).

(via WaSP Buzz)

Update: WordPress has posted their own announcement.

Update 2: MacManX has pointed out that lead WordPress developer Matt Mullenweg is a WaSP member, which helps explain the “Why WordPress?” question.

Update 3: I imagine the WaSP/Microsoft collaboration was probably a factor.

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 →

»All pages site-wide with this tag