Post a Comment
right here
http://releases.mozilla.org/pub/mozilla.org/firefox/releases/2.0b2/
WOW! I think I like it. Built in spell checker? Nice subtle graphical improvements. I have stuck with 1.0 until now I think.
Edited 2006-08-31 19:21
All of those are almost certainly in.
- a cairo based interface, called Thebes
- a new engine version (gecko 1.9)
Cairo/Gecko are basically the main change that 3 is supposed to introduce. There is no way I see them dropping this. If it isn't ready I expect them to delay the release instead of dropping it.
- Places (at least, yes, for 3.0)
Since this was supposed to be in 2.0 originally, it had better at least get into 3.0.
- a lot of bugs squashed
Obviously. All the known memory leaks are supposed to finally be corrected in 3.0, so that will be nice.
Does this version still have that odd window problem like the current one? I'm getting tired of going to a site where it opens up a new window (say a media player of some sort) and half the damn site is somewhere beyond the border. This has happened to me on many sites. Also noticed that some content won't show up on Firfox but would on say IE or Opera. Now maybe this is just my copy of Firefox, but from what I have heard this is not so. This was not an issue in earlier editions of Firefox. Well, I hope this situation has been attended to or will be in version 2.
I can:
go to : http://www.nyit.edu
and in Resources menu click on NYIT Connect - it opens in a new window although in settings I set it to open only a new tab. This is on Firefox 1.5.0.6 (Fedora 5)
They *work*, but often the developer of the extension just fails to update the extension to include the new version of Firefox as compatible. You either have to wait for the developer or use the Nightly Tester extension to override.
I don't think there's much of an elegant solution to it, besides perhaps Firefox building-in auto-update functionality for extensions (which currently does not exist).
No, same here and everywhere, of course.
When I read "Current users of Firefox 1.x should not use Firefox 2 Beta 2 and expect all of their extensions and plugins to work properly." I thought "Is this something new?"
It is one of the most unnerving feat^^bugs of Firefox, moreso given how often it is updated. The extensions system are one of this browser's greatest selling points and at the same time its greatest annoyance. I vent^^wrote about this in a short piece
http://www.nezmar.com/minefield-and-the-extensions-mess/
when trying out Minefield, a version of Firefox tailored for Mac OS X.
nda
when trying out Minefield, a version of Firefox tailored for Mac OS X.
Minefield isn't a version tailored for OSX, it is the trunk. IOW, it is what will someday become Firefox 3.0 and is currently very, very, very far from even alpha status. Which is why they called it "Minefield." You never know when it will blow up in your face.
I don't know how people can complain about 3rd party extensions not working with a pre-alpha or even beta product. Start complaining when they don't work with the 2.0 final release. Until then, if you expect things to work then you shouldn't be using betas anyway.
I'm cool with betas and alphas. Actually, and maybe I didn't make myself clear on this, the extensions mess isn't that much worse on Minefield than on Firefox.
My beef is with the mechanism of routinely disabling extensions plus the attempt to check for new versions coupled with the high rate of updates of Firefox which is frustrating, user-wise.
"it is what will someday become Firefox 3.0 and is currently very, very, very far from even alpha status. Which is why they called it "Minefield." You never know when it will blow up in your face."
Indeed. But you know what ? I am using it on a daily basis (building it from trunk sources) and they are very stable.
My today user agent :
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060901 Firefox/3.0a1
And the namecode of 3.0 will be "Gran Paradiso"
Source ?
http://www.google.com/calendar/embed?src=pdighgf028nmbjbrno8oed8vsg...
Still loving the new beta.
Maybe a bit overboard on the glassy/glossy icons - not sure.
One other thing is that close button on the ACTIVE tab should already be glowing imo. It seems to fit in better with the tab already being active if the close button is active also.
It does seem to use more memory but maybe that will be cleaned up before final or maybe it is just the nature of the beast.
Still love it though!



