Firefox 0.92
Dean
Firefox, the world's greatest web browser in my not so humble opinion, has been updated to version 0.92.
You know I was using Internet Explorer last night and I was shocked at how many popup ads I got assaulted with. I had forgotten how smoothly and seamlessly Firefox just makes those go away.









IE + googlebar = no popups
I'm looking at firefox, but it doesn't work with everything. I suppose I could clarify to say that it doesn't support all of the DHTML functions that IE does, or at least not with the same code.
Tabbed browsing is nice, which is why I like MyIE2.
And BigFire is right about spyware and other IE vulnerabilities.
That Google toolbar has caused my system to crash more than once. Funny thing? Google search is built into Firefox too...
I'm sure that it is compliant with the official html standards, and in all cases where I have had problems it certainly is because of the added features that IE supports. I have to ask though...when you have a 95% or greater market penetration...doesn't that become the standard by default? I'm sure that will make some folks angry, but the bottom line is that I cannot use Firefox for all of my work because it doesn't support everything that IE does. The fact that IE supports things not in the official standard means nothing to me. It does what I need and Firefox does not. Of course I accept that comes with some problems. The added features of IE create added vulnerabilities.
For most users I would say that Firefox is a superior browser to IE. For most internet pages it works great. I would probably recomment that the firefox team look at MyIE2's implementation of tabbed browsing, as I think it is better than theirs, but it is a great product.
I will be interested in seeing what the next IE looks like and how it compares to the next Firefox.
But IE doesn't add features; it often just does things differently, or in some cases, worse.
E.g. according to the DOM level 2 event model, an event handler should be passed an event object as its first argument, and it should be called on the element which generated the event. IE doesn't do this; it sticks the event object in some global variable (window.event) and then calling the event handler as a global function. That's not a feature, that's just not implementing the spec, and doing a bad job at it too.
The result is that you need to wrap your event handlers in a few lines of code to take care of this problem with IE, and also write a bunch of other annoying stuff to get around the scoping deficiencies of IE.
If that sounded like gibberish, just take this away: IE doesn't have extra features, it has extra bugs. Sometimes people write to these bugs, rather than writing to the standard and adding code to handle the bugs.
And tell me, does 95% of people thinking Pi = 3.14 really make it a rational number?
Of course we all lose our tempers now and then. Dean freely admits to being imperfect in this regard, which is why regulars to this establishment will generally be cut more slack than people who we don't know very well.
Still: behave like an adult, or go find somewhere else to play. Thanks.