Tag: Firefox

Posted on
by

The ridiculous Firefox/Opera rivalry (it’s software, not religion) has given rise to one annoyingly persistent meme: the belief that tabs are just MDI (Multiple Document Interface).

They’re not.

MDI, as implemented in many Windows applications and eventually abandoned by Microsoft, involves having a mini-desktop inside your application, with its own windows that you can minimize, maximize, and rearrange. If you have a taskbar-like interface it can look a lot like tabs, and you can certainly use it the same way as tabs, but it’s a different UI paradigm.

A tabbed interface is very specific. You have only one view at a time in your application window, and you switch between them based on a row (or column) of tabs along the window’s edge. You can look at it as a proper subset of MDI, but it is not the same thing.

Additionally, classical MDI uses one master window for the application. All documents appear in that window. Tabbed interfaces often (though not always) allow you to have more than one window, each with its own set of tabs. This makes it possible to group documents, web pages, etc. by category in a way that you can’t with a single-document interface or classic MDI.

So when people claim Opera had tabs first, they’re thinking of MDI—which Opera did have before Mozilla did. Tabs were showing up in browsers like Netcaptor and Galeon, however, long before they showed up in the Mozilla suite—and long before Opera hid its MDI capabilities under a tab-like veneer.

(reposted from Spread Firefox in response to Asa Dotzler’s post on the history of tabbed browsing)

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

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

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

Sorry 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 [CNET].

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.