I think the slightly updated look since the last beta looks much nicer (on the mac at least). I'm sure you'll still get people complaining, but I'm now a fan of the new look (I wasn't with the last beta).

Rusty

Is there any way to remove that useless "Go" button now? Before it was its own button but now it seems to be coupled with the URL bar.

Ack, the New theme still looks like crap on Linux.

This theme looks really bad on MacOSX as well, why not take some pointers from the pinstripe theme.. http://kmgerich.com/2006/09/27/pinstripe-for-firefox-now-with-20-more-macintosh/ Now *that* is a theme that is MacOSX worthy.

I've already got two (or three? can't remember) crashes in the last two days since the automatic update happened. Reported them through the automatic feedback tool.

Currently I'm running 2.0 at home and 1.5 at work. I hardly notice any difference. If you liked 1.5 you'll find yourself comfortable using 2.0. On the other hand, 2.0 is unlikely to have much important features that you can't get in 1.5 (i.e. I don't really miss 2.0 at work). There's of course some nice incremental changes in 2.0 but nothing to write home about. Most of the improvements you can get by installing extensions in 1.5 (e.g. all the tab stuff, spell checking, session restore, rss rendering, etc). That doesn't mean it isn't nice to have all those features properly integrated. Overall it doesn't look like a full year (I was running 1.5 beta's/RCs around this time last year) of development to me and that isn't surprising because most of the developers have been working on 3.0 where all of the more interesting things are happening it seems.

Also, I'm not enthousiastic about the new look. But then the previous theme wasn't that good either (kind of dull and icons are poorly designed). The main feature of the new theme seems to be that it is different, not that it is better. To be honest, it seems a bit like a rushed job motivated primarily by a need to defend the 0.5 version increment (why else would it have been landed after the feature freeze). However, it's good enough that I won't install a third party theme. The discussion about the version number is of course not really worth the trouble, so lets move on and get 3.0 going.

at least when it comes to configuring cookie management: why on earth did they remove the option to not accept cookies unless they are from the original domain? Instead of removing this very useful configuration feature they should have added a feature to not execute Javascript that is not from the original domain. Do they get paid from commercial sites that use this as a tracking and statistics device for removing that useful feature?

I'm a tiny bit disappointed, it freezes up after opening and displaying the first page under Windows 95. I noticed that removing the file nsUrlClassifierLib.js will let it mostly run, although I think whatever that does it is just calling whatever function is causing the actual freeze as certain web pages will still cause Firefox to freeze.

(And before anyone asks why Windows 95... Because I can! Oh, and no IE!)

I wonder why Firefox needs their own set of dictionaries? Many people already do have OpenOffice dictionaries with their own exceptions/additions which are available for a big number of languages. Why not allow to use them? Or more generally, make spelling dictionaries pluggable as OpenOffice does (at least on Linux)?

Is there an option to have the old style close-tab button, where there is just one fixed-position close-button for all tabs? Or is this something that themes can implement?

Having a separate close for each tab can be nice, but I find that I more often want to close a lot of tabs - and having to move my mouse around to close them is, well, less efficient... (There's always the keyboard ofcourse, but for me the mouse feels more natural when surfing)

I can't find the chekc box option allowing you to set if firefox should trim images by default anymore. Anyone know where that option is in this RC?

The transition experience is much better than IE 7.

So far I see two problems : 1, In window.open(), the "dependent" attribute does not work any more. 2, In some cases, the "View Selection Source" window freezes.

I've had no problems at work but at home I'm having a few problems with RC1. First off being that when i go to log into bugzilla there's no response when I enter my login details. The next problem is that I have a space for the bookmarks toolbar, and the bookmarks appear in the bookmarks toolbar on the bookmarks menu, but nothing is appearing on the bookmarks toolbar itself. The last problem is that I can't use multiple tabs. When i go to open a new one and select it, the address bar does not synchronise. Even though the tab is in the foreground, when I enter something in the address bar, it just overwrites the first pane rather than the one I'm working with.

My add ons are: chatzilla 0.9.75 google toolbar for firefox 2.1.20060807W Html validator 1.2.2 (htmlvalidator.com) Talkback 2.0 (which reports it isn't compatible with Firefox 1.5.0.7 even though the Browser about says Firefox 2.0) Web developer 1.0.2

Any ideas?

Great great release overall, some points...

1. Only accept cookies if from original domain, simply must remain, this is too crucial a security function to remove. 2. Back/Forwards - b2 corrected the long standing issue of the drop down seperator not showing upon hovering over it. Please correct this simple thing. 3. Bookmarks arent used by the majority of the web as per google research, so its clutter to the majority. 4. Go icon is basically a forwards button, it should be an enter arrow to make clear it has the same loading effect as enter. 5. Tabs minimum size should be bigger, and close buttons should remain on each tab. Changing this is un subtle and shows close on each tab as not working when it does it more usable mimimum tab sizes remain. Plus the more tabs there are, the more helpful and efficient a tab close on each tab is.

Great great release overall, some points...

1. Only accept cookies if from original domain, simply must remain, this is too crucial a security function to remove. 2. Back/Forwards - b2 corrected the long standing issue of the drop down seperator not showing upon hovering over it. Please correct this simple thing. 3. Bookmarks arent used by the majority of the web as per google research, so its clutter to the majority. 4. Go icon is basically a forwards button, it should be an enter arrow to make clear it has the same loading effect as enter. 5. Tabs minimum size should be bigger, and close buttons should remain on each tab. Changing this is un subtle and shows close on each tab as not working when it does it more usable mimimum tab sizes remain. Plus the more tabs there are, the more helpful and efficient a tab close on each tab is.

The latest release looks nice. Now hopefully all the extension developers will begin updating their extensions and not wait until the last minute.

I've seen Fx 2 and 1.5 both on Windows and Fedora, The 1.5's theme is great, unfortunately 2's theme suxs...

I hope Fx2 is released with 2 built-in themes like SeaMonkey or Mozilla Suite (having Default and Modern themes built in)

PS: Again, ... didn't like 2's theme.

"Visual refresh" finished very fine in RC1 (previous beta was not very good at this point). Only one exception: I don't like home button somehow. After 2-3 days of testing I didn't find any annoyance in product functionality or stability. Good work. Looking forward to 2.0

I really like 2.0 except one new "Feature" completely breaks my web application. We have an application for managing the companies documents where everyone can upload and retrieve all of our product documentation. When people are wanting to view a document we stream the file from the database using an application/octet-stream mime type so that they get the option to either save the file to their disk for later use or open it to view it. In IE, FF1.0 and FF1.5 this works great. In FF2.0 we only get the window to save to disk. I figure this was probably done for security, but the window tells me I'm downloading a Word document so why can't I open it in Word. I can see if I checked it to always say download for that type but I don't even have that option.

Following customization from http://www.mozilla.org/unix/customizing.html#usercss which was working with FF1.5 is no longer working with FF2 rc1. /* Place the sidebar on the right edge of the window */ window > hbox { direction:rtl; } window > hbox > * { direction:ltr; }

At first when trying out beta 2, I thought the glowing buttons did not have enough contrast (against the bright background of the default theme). In RC1, the problem seems to have been solved by making the theme background darker. However, given the choice between a darker background and the lighter one, I would definitely prefer the lighter one. Going back to check out beta 2 again, I also came to think that the contrast on the glowing buttons is actually good enough, since it is noticeable. (By the way, I do like the fact that the New Tab button is a fully button again, rather than one that just goes down partially.)

The Go button. Some people apparently like to have it not be there at all. I like to have it on the left. (I also prefer the old look of the button to the new look). Is there any chance of going back to the way it is in v1.5?

I find the non-active tabs in RC1 to be rather dark. In v1.5, the active and non-active tabs are both bright (which I like), but have enough of a difference in color to be noticeable, and I also like the color bar across the top of the active tab (helps a lot). On the other hand, in beta 2, there was not enough of a contrast in color between the active and non-active tabs (and there was no color bar on the active tab, which did not help). The solution in RC1 seems to be to make the non-active tabs darker. Any chance of going back to the way it is in v1.5?

Doing that would probably make the glowing buttons harder to differentiate - but, as I noted, I suspect they are good enough anyway, contrary to my earlier sense of the situation.

I do like the close button on every tab - as long as there is a tab list that makes it possible to quickly and conveniently switch to a tab that is not on screen because of the need to have the tabs be larger than before, as a practical matter, when they get small, due to the real-estate that the close button takes up on each tab.

Does anybody know if there's work on a Canadian English spell-checking dictionary for Firefox 2.0? The extensions site only has dictionaries for UK and Australian English.

If not, I'd like to contribute to the effort. How would I go about creating my own spell-check dictionary extension?

Does anybody know if there's work on a Canadian English spell-checking dictionary for Firefox 2.0? The extensions site only has dictionaries for UK and Australian English.

If not, I'd like to contribute to the effort. How would I go about creating my own spell-check dictionary extension?

Does anybody know if there's work on a Canadian English spell-checking dictionary for Firefox 2.0? The extensions site only has dictionaries for UK and Australian English.

If not, I'd like to contribute to the effort. How would I go about creating my own spell-check dictionary extension?

Sorry for the multiple postings. I maintain a whitelist of cookies, and since mozillazine wasn't part of that list, I didn't get the confirmation messages, but that posts actually went through.

Sorry for the multiple postings. I maintain a whitelist of cookies, and since mozillazine wasn't part of that list, I didn't get the confirmation messages, but that posts actually went through.

The dictionary spell checker is a very good feature, but after some further thought and reading the above comments, I'm growingly concerned its been a little rushed. Its very disappointing dictionaries are not being shipped with a lot of builds. At RC1 stage is worrying such basic matters aren't being better dealt with and implemented. This is really not good and its not totally clear to what extent if any this may be the case the final release. Also given past experience, I don't think Mozilla are giving locals matters like this quite enough of the attention it deserves. After Konqueror Mozilla are to be fair probably the best with locales, but still improvements needed. You don't get more fundamental with a browser than languages, there's been past problems with locales being released on time and its improving. This has a dangerous smell of the same mistakes being made due to a lack of solid organisation and efforts to fundamentally improve and ensure timely release of dictionaries for ALL languages of the world.

As per previous comments here I sense there's fundementally better ways to implement spell checking such as linking to dictionaries, office suites being an obvious source as users who have they're dictionary with all additions of words, should not have to go all the way through doing the same for the same language spell checker in another basic application. Great feature, but been rushed me thinks. Anyone have further information, thoughts...?

Also, having to go through your document looking for red lines on words and right clicking each and every one is a bit of a long winded un-efficient way of spell checking, a one click spell checker button bring up a box going through all words, is basic efficiency and what users are used to and expect. No matter how good a feature is, if its not ready, improve it, make it ready, then release. This growingly has "rushed" all over it.

It seems they have totally crippled the preferences in this release, removing a lot of very useful things for no apparent reason. Apart from the cookie option to accept cookies only from the original domain I cannot find the options for whether or not to show the download dialog or where to download files to. What can the motivation for such an idiotic removal be? I have just thrown away RC1 and reinstalled 1.5 -- I am not in the mood to configure my browser by hacking about:config all the time.

I'm really loving RC1. I've completely uninstalled 1.5.0.7. First of all, RC1 is fast and stable on my machine. No crashes or glitches. Nothing out of place or missing in the interface. And all my user data migrated over nicely and shows up fine. What I like are the spellcheck (I could not get Spellbound to work in 1.5.0.7); the session saver; and what seems like increased speed. I'm even getting used to the separate close buttons on each tab. It's superior to the previous way tabs were handled. Managing bookmarks is easier now too with the double panes (or did I just miss that feature in previous releases?). So kudos to the team of developers who put this out. It puts Microsoft to shame. IE is an ancient slug compared to RC1.

I'm really loving RC1. I've completely uninstalled 1.5.0.7. First of all, RC1 is fast and stable on my machine. No crashes or glitches. Nothing out of place or missing in the interface. And all my user data migrated over nicely and shows up fine. What I like are the spellcheck (I could not get Spellbound to work in 1.5.0.7); the session saver; and what seems like increased speed. I'm even getting used to the separate close buttons on each tab. It's superior to the previous way tabs were handled. Managing bookmarks is easier now too with the double panes (or did I just miss that feature in previous releases?). So kudos to the team of developers who put this out. It puts Microsoft to shame. IE is an ancient slug compared to RC1.

I'm really loving RC1. I've completely uninstalled 1.5.0.7. First of all, RC1 is fast and stable on my machine. No crashes or glitches. Nothing out of place or missing in the interface. And all my user data migrated over nicely and shows up fine. What I like are the spellcheck (I could not get Spellbound to work in 1.5.0.7); the session saver; and what seems like increased speed. I'm even getting used to the separate close buttons on each tab. It's superior to the previous way tabs were handled. Managing bookmarks is easier now too with the double panes (or did I just miss that feature in previous releases?). So kudos to the team of developers who put this out. It puts Microsoft to shame. IE is an ancient slug compared to RC1.

The Mail icon that can be added to the Navigation Toolbar is missing in RC1. This has been really handy for me. RC1 looks good and works for me except for extensions. On the surface not much new.

When I go to the download page for Firefox 2.0 RC1, I get 1.5.0.7 instead.

This is for windows English.

Does anyone else get this problem?

I have no idea why this happens, but if I am in Firefox 1.5.0.7, then I get the wrong download.

But if I go to IE 7, RC1, it works fine.

I get the right download.

Does anyone know why this happens?

OK, I now see what happened.

When I went to the download page it sent me to a page where javascript was blocked, and I did not unblock it.

Why that sent me to the download of 1.5.0.7 rather than 2.0 RC1 is beyond me.

I would have expected that it might block the download completely, but not send me to the wrong one.

This Fx is what I expected 1.5 to be in the areas of speed. The features of note to me is the session saver & the tabs its nice to have the control over them as default. At least now having tab control doesn't mess with other extensions. I had nothing but trouble with the tabrowser ext. The only thing I don't get is the spell check. I'll go to the Fx forums to find out how they work. Thank you to the Moz Devs.

It tried the partial update, failed; tries the full update and then (after downloading it and halfway through the progress bar you get when running it after that) appears to fail and dump me back in beta 2. Hrm. At least it didn't leave the browser unloadable...

I'm going to try downloading it from scratch. I guess most people updating from beta 2 had a successful experience though as there aren't any other posts here?

--sam

The tabs are particularly handy, since I tend to run Fx with plenty open tabs.

What happened to the "for originating site only" cookies option. Although I clear the cookies when I close Fx, it would be nice to know the advertisers are tracking my movements.

Session saver -- fab. I've left my machine running for a number of days, and experienced it's effectiveness. It'll certainly help me switch off more regularly and become a little more green. But where is the menu option to use it? Is this another option that needs to be set via about:config? I'm hoping we're not making about:config the first port of call for config changes.

Otherwise great! Although the little I've played with IE7, Fx is going to struggle to gain in enterprise networks. I'm happy to say, more and more people I talk to and advise on IT stuff are using Fx, even non techies. And that's good for Fx.

To add another point about modal dialogs, the window.open dependent flag is only one possible workaround that we now seem in danger of losing. It would be fine if we had full support for EITHER the 'dependent' flag or the 'modal' flag, but now we appear to have neither. Right now, the modal flag doesn't provide true "application modal" behavior, it simply provides a means of keeping a dialog window on top of the parent window, but fails to provide event capture, and therefore makes it possible for a normal user to access the underlying parent window while the modal dialog is active. That's very bad; the user can invoke other functions on the parent window or worse yet, close it, leaving the modal dialog window stranded without a context, and floating behind other windows (now that the dependent flag is in danger of being discontinued). Imagine something as simple as a date selection calendar popup window, in IE one line of code gives you a true modal dialog that remains above the parent form window and captures evens to prevent a user from doing anything else until the popup is closed. In Firefox, you can use window.open with the modal flag to do the same thing, but the user is free to click on the parent window while the popup is active, and is free to close the parent leaving the dialog stranded or lost. Worse still, the lost copy then prevents the calendar popup from reappearing the next time the parent is opened and the dialog is invoked! It's imperative we start taking the importance of modal dialogs more seriously, it remains one of the key differentiators between IE and FireFox, despite all the other great application development features in FF. We were on the verge of making FireFox a supported option for our web based applications, with FF 2 moving backwards on modal dialog functionality, there's just no way.

To add another point about modal dialogs, the window.open dependent flag is only one possible workaround that we now seem in danger of losing. It would be fine if we had full support for EITHER the 'dependent' flag or the 'modal' flag, but now we appear to have neither. Right now, the modal flag doesn't provide true "application modal" behavior, it simply provides a means of keeping a dialog window on top of the parent window, but fails to provide event capture, and therefore makes it possible for a normal user to access the underlying parent window while the modal dialog is active. That's very bad; the user can invoke other functions on the parent window or worse yet, close it, leaving the modal dialog window stranded without a context, and floating behind other windows (now that the dependent flag is in danger of being discontinued). Imagine something as simple as a date selection calendar popup window, in IE one line of code gives you a true modal dialog that remains above the parent form window and captures evens to prevent a user from doing anything else until the popup is closed. In Firefox, you can use window.open with the modal flag to do the same thing, but the user is free to click on the parent window while the popup is active, and is free to close the parent leaving the dialog stranded or lost. Worse still, the lost copy then prevents the calendar popup from reappearing the next time the parent is opened and the dialog is invoked! It's imperative we start taking the importance of modal dialogs more seriously, it remains one of the key differentiators between IE and FireFox, despite all the other great application development features in FF. We were on the verge of making FireFox a supported option for our web based applications, with FF 2 moving backwards on modal dialog functionality, there's just no way.

To add another point about modal dialogs, the window.open dependent flag is only one possible workaround that we now seem in danger of losing. It would be fine if we had full support for EITHER the 'dependent' flag or the 'modal' flag, but now we appear to have neither. Right now, the modal flag doesn't provide true "application modal" behavior, it simply provides a means of keeping a dialog window on top of the parent window, but fails to provide event capture, and therefore makes it possible for a normal user to access the underlying parent window while the modal dialog is active. That's very bad; the user can invoke other functions on the parent window or worse yet, close it, leaving the modal dialog window stranded without a context, and floating behind other windows (now that the dependent flag is in danger of being discontinued). Imagine something as simple as a date selection calendar popup window, in IE one line of code gives you a true modal dialog that remains above the parent form window and captures evens to prevent a user from doing anything else until the popup is closed. In Firefox, you can use window.open with the modal flag to do the same thing, but the user is free to click on the parent window while the popup is active, and is free to close the parent leaving the dialog stranded or lost. Worse still, the lost copy then prevents the calendar popup from reappearing the next time the parent is opened and the dialog is invoked! It's imperative we start taking the importance of modal dialogs more seriously, it remains one of the key differentiators between IE and FireFox, despite all the other great application development features in FF. We were on the verge of making FireFox a supported option for our web based applications, with FF 2 moving backwards on modal dialog functionality, there's just no way.

This flaw reported by Mozilla http://www.mozilla.org/security/announce/2006/mfsa2006-59.html is still unfixed in the latest Firefox 2.0 final.

This exploit works in Firefox 2.0 Final: http://lcamtuf.coredump.cx/ffoxdie.html

"Jonathan Watt and Michal Zalewski independently reported timing dependent testcases that trigger crashes at the same place during text display. We have seen no demonstration that these crashes could be reliably exploited, but they do show evidence of memory corruption so we presume they could be. Note: Thunderbird shares the browser engine with Firefox and could be vulnerable if JavaScript were to be enabled in mail. This is not the default setting and we strongly discourage users from enabling JavaScript in mail."

by SecurityFocus

__________________

Suggestion:

The Firefox could load extensions in real time without needing to close and to come back to open and did not have to allow to the extensions crash.