Reply to: Firefox 3

[crack_ho]

The final version is the same as RC3.

[KevinS]

Well the Firefox download page is unavailable at the moment, so I'm guessing they've released version 3 final.

Managed to download it at 8:30 or so last night.. Is VERY quick at rendering..

[voodooflux]

Well the Firefox download page is unavailable at the moment, so I'm guessing they've released version 3 final.

[realityhack]

JFGI

I like that term. I shall be using that at clientco forthwith. Cheers NF.

[voodooflux]

Geek factor = 1 googolplex

Is that good?

[voodooflux]

snip

That's interesting, and an entirely reasonable assertion.

[Moscow Mule]

Geek factor = 1 googolplex

[NickFitz]

Kudos to Microsoft for finally recognising that, although there is the danger that with a completely new engine we end up effectively having to target another browser.

FWIW, I have reason to suspect that they're building on the IE5-Mac engine Tasman, which was a good implementation of most of CSS 2 and should therefore provide a solid basis for a good CSS 2.1 implementation.

This suspicion is based on the fact of an obscure comment-parsing bug in IE5-Mac also being present in the first IE8 beta - it seems very unlikely that such an obscure bug would be created twice independently, and Tantek Çelik (who wrote Tasman) no longer works for MS, so it's not somebody making the same mistake twice.

It makes sense really - if you've got a working (though outdated) implementation just sitting there gathering dust, you might as well start with that

[voodooflux]

Yep - they haven't ported it to Ubuntu yet.

Any hardcore Ubuntu user should be using Lynx anyway

[Peoplesoft bloke]

Why, is there something wrong with Internet Explorer?

Yep - they haven't ported it to Ubuntu yet.

[Peoplesoft bloke]

I've had version 3.0 for weeks already

WHS

Mine's the Beta version though.

[voodooflux]

It still has some truly awful bugs though, including some that IE6 doesn't have.

Such is the path of software "progress"

Agreed, it's an improvement, but not enough of one, which is why MS have now officially accepted that it's a dead code path. Apart from anything else, its reliance on the internal hasLayout construct means that some aspects of CSS2.1 could never be properly supported.

Kudos to Microsoft for finally recognising that, although there is the danger that with a completely new engine we end up effectively having to target another browser.

[NickFitz]

It's a helluva lot better than IE6 was - it became much easier to achieve consistency between IE7 and Firefox.

It still has some truly awful bugs though, including some that IE6 doesn't have.

Agreed, it's an improvement, but not enough of one, which is why MS have now officially accepted that it's a dead code path. Apart from anything else, its reliance on the internal hasLayout construct means that some aspects of CSS2.1 could never be properly supported.

[voodooflux]

IE7? The one Microsoft have abandoned development of, opting for a completely new rendering engine for IE8, because they've finally accepted that it's impossible to fix?

It's a helluva lot better than IE6 was - it became much easier to achieve consistency between IE7 and Firefox.

[NickFitz]

Any easy ways to install and run two different versions at the same time, as there is with 'multipleIEs'?

You need to install them in their own folders, then create a separate profile for each one.

Details differ slightly depending on OS, so JFGI