MozillaZine

Mozilla Firefox 2 Release Candidate 2 Available

Friday October 6th, 2006

Mozilla Firefox 2 Release Candidate 2 is now available for download. Users of Mozilla Firefox 2 Release Candidate 1 can upgrade using the software update feature.

For more information, refer to the Release Notes.


#1 What's new?

by mernen

Friday October 6th, 2006 9:57 PM

Reply to this message

I couldn't find anywhere what exactly is new in this release (compared to RC1). Could anyone inform?

#2 Firefox Portable 2.0 RC2: Test Without Installing

by CritterNYC

Friday October 6th, 2006 11:09 PM

Reply to this message

Firefox Portable 2.0 RC 2 has been released. For the unfamiliar, Firefox Portable is Firefox packaged with a PortableApps.com launcher so it can be run from a USB flash drive, iPod, portable hard drive, CD, etc and used on any computer. It can also be run from a local hard drive (even your desktop) making it a great way to test out another version of Firefox without impacting your installed version. Grab it from the Firefox Portable 2.0 RC2 Homepage: <http://portableapps.com/a…net/firefox_portable/test>

#3 Firefox 2 is a bit of a disappointment

by fiend

Saturday October 7th, 2006 3:15 AM

Reply to this message

They should have made it more stable, faster, more memory efficient, and cleaned some idiotic bugs that have persisted since firefox exists, like the copy paste problems, firefox was meant to be a very clean efficient browser, they should just keep it firefox, if they want spellcheck/phising/whatever they should release it has an "official" extension, or maybe release a "general version firefox" with all the official add-ons and a "clean version firefox" ... well now opera is looking more and more streamlined...

#4 Great release

by krissilver

Saturday October 7th, 2006 5:01 AM

Reply to this message

Fiend thats a very biased rant showing little understanding or consideration of general usability for general users. Most people dont experience serious problems with Firefox hence why its regarded as one of the if not the best browser out there. So whilst valid, your seriously exaggerating the seriousness of some bugs and other points you make. I too would like to see memory usage really improved, less toolbars as Fx has the most toolbars and clutter, and other bugs fixed. But Inline spell checking, phishing protection, are so basic and essential they warrant being a part of the browser for all users. Why, because a majority of web users write text be it in forms, emails on the net, and spell checking is a very basic thing to have. Phishing is a very serious online threat that all should be protected from, not a chosen few.

Add-ons are for things which are deemed not necessary to be in the default build as they dont benefit the majority, but even if its a small thing that benefits a minority, if it doesnt impact the majority adversely, it is still valid for it to be considered in Firefox. You totally contradict your argument by saying how good Opera is. Yes they have some fine features some of which Fx have now implemented. Great.

That's the basics. If you want bugs fixed, vote on them, help with them, report your problems, add comments, send feedback to Mozilla.

Firefox 2 is a great release. It would be nice to have noted somewhere the differences between RC1 and RC2 as per mernen's comment. In general I think with Firefox now dealing with web pages as tabs throughout (great) its sensible then to have a common thing as a "new tab" button. As an intended clean and simple browser, the Firefox interface has more toolbars, information, buttons compared with most other browsers now, particularly Opera and IE. This needs addressing urgently, theres no reason why a basic browser should be showing the most toolbars, most information, and most buttons compared with other browsers, more UI cleaning up, better space using, choosing what really needs to be in the UI, and innovation is needed. In particular the bookmarks toolbar, when bookmarks are used less and less and no other browser has an entire bookmarks toolbar, Firefox should not either. It clutters for the majority and isnt necessary. Nor is the status bar, load bar should be on each tab to be able to see loading status of each page without clicking on it. Link addresses should be upon the hover. Little else is used from it.

Great release as a whole.

#15 Re: Great release

by ronin65

Saturday October 7th, 2006 9:08 PM

Reply to this message

This release is doomed not to be even tried by the vast majority of Firefox users. There would have been no downside to postponing its release other than the bruised egos as a result of the delay.

As most extensions are not FX2 compatible, most users will not be inclined to try it. Because of the incompatibilities with existing profiles even fewer will want it.

Progress sometimes casuse problems like this, but I think the timing is suspect at best.

Firefox without the extensions to civilize it is not what it could or should be. The argument persists that "you don't need..." whatever features, but that misses the point in my view. "Nobody" wants a command line browser any more, but it is the ultimate "lean browser".

Even if FX2 is "a great release" not many people will care. It is just the wrong thing at the wrong time.

#26 Re: Re: Great release

by leafdigital

Tuesday October 10th, 2006 2:45 AM

Reply to this message

And what would be the upside in postponing its release? I don't see one. You're not going to get more features; the features were planned ages back.

Already most of my extensions have been upgraded for Ff2. Those that haven't I'm sure will follow either before, or very soon after, the official release. I fully expect the vast majority of Firefox users to upgrade to Ff2, especially if the auto-update pushes it.

The interface (as of RC1, haven't restarted to get RC2 yet) is improved over the betas and looks good; the session saver thing is nice; overall it's a significant but not massive improvement over 1.5.

--sam

#28 Re: Re: Great release

by FattMattP

Tuesday October 10th, 2006 9:26 AM

Reply to this message

> This release is doomed not to be even tried by the vast majority of Firefox users.

Duh! No kidding. That's why it's a RELEASE CANDIDATE. It's for developers, not end users.

> As most extensions are not FX2 compatible

That's not Mozilla's problem. If you have extensions that don't work then write to the author and ask them to update their extensions.

> Even if FX2 is "a great release" not many people will care.

You are correct that they won't care. The auto update will update them to FF2 without them having to do anything. They'll keep on surfing and not worry about anything.

#48 Re: Re: Re: Great release

by ronin65

Sunday October 15th, 2006 10:45 AM

Reply to this message

Duh!!!

You miss the points completely! The extensions which are not up to FX 2 are more important to more people than FX2 and, yes, it is Mozilla's problem as the browser is pretty crude without them. The benefits of FX2 to most people are virtually non-existent.

When the autoupdate screws up an install that was working perfectly well FX will get a well deserved bad reputation.

#21 Re: Great release

by epohs

Monday October 9th, 2006 8:37 AM

Reply to this message

I would recommend that certain features that are deemed necessary to be in the default build (such as "View Source", "Page Info", the Error Console, etc..) be made optional 'extensions' that are included by default... Think DOM Inspector here. Because, I think they are very useful tools, but possibly not equally necessary to every user across the board.

While I may not share ALL of fiend's tone, I do hope the FF devs remember the minimalist drive that caused Firefox/Phoenix to split from the full Mozilla suite in the first place.

#29 Re: Re: Great release

by leafdigital

Tuesday October 10th, 2006 9:59 AM

Reply to this message

From a developer's point of view it's handy if everyone has those tools installed (e.g. somebody reports a problem, you call up and ask them to open the error console and what do they see, etc). Making them optional wouldn't be a terrible idea but in that case I would urge them to ensure that the tools are extremely easy to install via the mozilla update website, and you don't have to reinstall or anything.

--sam

#24 Re: Great release

by BenoitRen

Monday October 9th, 2006 11:16 AM

Reply to this message

> If you want bugs fixed, vote on them

Votes don't mean anything.

#27 Customize it!

by neilparks1

Tuesday October 10th, 2006 6:12 AM

Reply to this message

(quote)

> "... the Firefox interface has more toolbars, information, buttons compared with most other browsers now, particularly Opera and IE. ... theres no reason why a basic browser should be showing the most toolbars, most information, and most buttons compared with other browsers, more UI cleaning up, better space using, choosing what really needs to be in the UI, and innovation is needed. In particular the bookmarks toolbar, when bookmarks are used less and less and no other browser has an entire bookmarks toolbar, Firefox should not either."

(end quote)

That's what the "customize" feature is all about. (View/Toolbars/Customize, or right click on the toolbars.)

If there are buttons on your toolbar you don't need, you can remove them. Don't want a bookmark toolbar? Turn it off. Or move it up to where the menu bar is. You decide.

That has always been one of Firefox's best features.

#30 Re: Customize it!

by BenoitRen

Tuesday October 10th, 2006 10:37 AM

Reply to this message

You forget that another one of Firefox' best features are sensible defaults. This doesn't look like that.

#41 Re: Great release

by ddr513

Wednesday October 11th, 2006 3:46 PM

Reply to this message

>>Fiend thats a very biased rant showing little understanding or consideration of general usability for general users. << Which is not to say, of course, that some of the problems fiend pointed out *do* exist. Criticism does not necessarily equal rant. >> If you want bugs fixed, vote on them, help with them, report your problems, add comments, send feedback to Mozilla. << BenoitRen is right. Won't matter much.

#5 Search for text when I start typing?

by joe222

Saturday October 7th, 2006 6:25 AM

Reply to this message

Where did the options go? I loved to be able to highlight everything. All of a sudden this only highlights one instance!

I converted so many people to firefox and the only two things I ever showed them so they would stick to it would be tabs and search for text when you type. But the latter was relevant not only by itself, but also by being able to hightlight all instances of the searched term.

And this is the most strange when Safari just got this:

<http://images.appleinsider.com/mom-safar3-1.jpg> <http://appleinsider.com/article.php?id=2111>

Any one can give an explanation for this?

#6 Re: Search for text when I start typing?

by Karlosak

Saturday October 7th, 2006 7:25 AM

Reply to this message

I'm also annoyed by the "find as you type" behavior. I though that the function was stripped only for the development stage (betas), but with the release candidate out, I'm afraid there is little hope for the old (much more usable) Fx1.5 behavior. I know, it's easy to press CTRL+F, but why to remove such usable function? From a programmer standpoint, the complexity wouldn't be increased (reduced). It's a really bad habit to remove useful features already included in the previous Fx versions, especially when the browser's simplicity or download size isn't affected.

The same can be said about the Options menu. Where is the option "Allow cookies for the originating site only" and "Resize large images to fit in the browser window"? I'm really perplexed by this.

Last, Firefox 2 runs noticeably slower than Fx1.5.0.7 on my computer (P3 550Mhz, 640MB RAM), even with no extensions! Especially tabs switching/opening/closing and general browser response to commands is worse. If things don't change (little chance by now), I'll have to stay with the Fx1.5.x branch. Sad to say.

#8 Re: Re: Search for text when I start typing?

by neongroove

Saturday October 7th, 2006 7:54 AM

Reply to this message

Nothing has changed in my install of RC2. Just go to Tools -> Options and click on the "Advanced" tab.

#9 Re: Re: Re: Search for text when I start typing?

by Karlosak

Saturday October 7th, 2006 9:21 AM

Reply to this message

Yes the function itself works, however its possibilities were reduced. Only one instance could be found. There is no way to cycle through all the occurrences of the searched expression, no way to highlight all of them. Surely you can press CTRL+F and gain all the functionality, but it slows down my web browsing. It bugs me that useful features are being stripped down from the previous versions and new ones are added from which some could be installed through extensions and don't need to be in the plain browser, that's all. Maybe I've found a bug or there is some hidden option in about:config to recreate the old behaviour, so please tell me if you know. I'm running the windows build btw.

#10 Re: Re: Re: Re: Search for text when I start typin

by crox

Saturday October 7th, 2006 10:33 AM

Reply to this message

F3 works for me, perfect as when I've typed in what I'm looking for I don't want to go back to the mouse

#13 Re: Re: Re: Re: Search for text when I start typin

by Picklesworth

Saturday October 7th, 2006 3:24 PM

Reply to this message

Not sure what the problem is here...

I can type any random thing and as long as a form isn't selected a little search box appears. It's a rather nice search box as well, in my opinion, since it works in a very quick way; pressing anywhere outside the Quick Search box makes it go away and I don't have to erase its old contents when I start it back up. (I can't stand leaving stuff in there after a search!)

Just press Ctrl+G to search again :)

I think the idea was to make it a more casual and quick feeling search box, and I think it worked.

#7 Re: Search for text when I start typing?

by baka_toroi <epremuz@propuh41.com.ar>

Saturday October 7th, 2006 7:35 AM

Reply to this message

I might be somewhat stupid, but what is the behaviour that has changed in this release? I can still find as I type and highlight all the matches.

#11 Re: Re: Search for text when I start typing?

by joe222

Saturday October 7th, 2006 10:39 AM

Reply to this message

The options that you have now showing up when pressing Ctrl+F showed up as soon as you started typing, no need to press Ctrl+F after that.

Having said this, what I'm not happy with is a missed chance. If the extra controls have been removed for simplicity (can agree with that) the default option should have been enhanced to highlight _all_ instances of the searched term. And then that could have been improved by highlighting the selected occurrence in a special way, just the way that Safari does in the screenshot provided above.

But just showing one occurrence the feature seems almost without merit (do it is not compared to a browser without the feature at all). A pity. Hopefully as people start seeing the advantages of highlighting every occurrence by default in Safari, there will be an easier chance that Firefox picks this up in version 3 (or one can always hope)

#12 Re: Re: Re: Search for text when I start typing?

by Gnerma

Saturday October 7th, 2006 11:49 AM

Reply to this message

This has been a major issue of contention in the forums over the last few months. I personally believe its a change that'll be an unpleasant surprise to the majority of users who employ FAYT. If you take issue with this change please direct your attention to this bug:

<https://bugzilla.mozilla.…rg/show_bug.cgi?id=347259>

#22 Old School FAYT

by hhh

Monday October 9th, 2006 10:51 AM

Reply to this message

Add the following to userChrome.css to get the old Quickfind bar...

/* Old School Find Bar */ #FindToolbar > * { display:-moz-box !important; }

#16 Re: Search for text when I start typing?

by voracity

Saturday October 7th, 2006 11:20 PM

Reply to this message

So, what are the functional differences between QuickFind and Find? So far, I've found these:

* QuickFind dialog disappears after a few inactive seconds * QuickFind selects the link elements it finds (so you can hit enter)

Are there any others? If not, why not make QuickFind and Find the same thing? (Except for the dialog timeout.)

If they are not to be joined as one, could I at least suggest making 'Tab' open the selected link in Find (like an autocomplete), since it does nothing useful right now.

#14 How to do automated installs

by rduke

Saturday October 7th, 2006 3:32 PM

Reply to this message

Nowhere in the announcement did I see a link to some install instructions for administrators. Will this ever be addressed? Most individuals who would want FF already have it on their PC. Wouldn't you guys want admins to deploy it in businesses now?

How do I install it on 50 PCs? Into a specific folder, along with some extensions, custom bookmarks, and pre-configured for all users?

Please start considering the needs of administrators who would like to test FF, but who cannot install it manually on all PCs.

Can the app folder just be copied to another machine into some folder and work?

How can a default profile be pre-configured? Which files need to be edited? What has to be edited? Where can we use environment variables (%USERNAME%, %APPDATA%, etc.), and special folders (Desktop etc.)

#45 Re: How to do automated installs

by wayneo

Friday October 13th, 2006 4:32 AM

Reply to this message

This should be able to help you

#46 Re: Re: How to do automated installs

by wayneo

Friday October 13th, 2006 4:33 AM

Reply to this message

#47 Re: Re: Re: How to do automated installs

by rduke

Saturday October 14th, 2006 11:45 AM

Reply to this message

You must be kidding. Step 2 in your link (<<http://varun21.blogspot.com/>>) is "Compiling the source into a build." So I have to buy a fucking compiler now?

#17 Find and Quick Find

by Galik

Sunday October 8th, 2006 5:17 AM

Reply to this message

I found that if you do Ctrl+F for Find you can set the heighlight all flag. From then on the Quick Find will indeed heighlight all!

Once you get used to it the old functionality is still there it ust needs discovering!

#18 Huge concern

by krissilver

Sunday October 8th, 2006 5:37 AM

Reply to this message

I'd just like to note again a big concern noted several times already but worryingly not being dealt with. The Security/privacy option of "allow cookies from originating site only" has been outright taken away. This simple privacy feature existed since early Fx versions and even now exists in IE and other browsers. Its a very basic privacy/security feature, and with the addition of many things in the options window, in no way is it justified to take away such a basic privacy/security feature. This needs urgent attention as its been extremely underrated and will lead to problems, and people percieving Firefox to be taking away basic security/privacy features but adding other lesser known or needed features, and thats basically correct. This needs an urgent re-think.

#19 Re: Huge concern

by kRush

Sunday October 8th, 2006 6:46 AM

Reply to this message

Couldn't agree more, though it's listed as wontfix on bugzilla (<https://bugzilla.mozilla.…rg/show_bug.cgi?id=349680>). One can get the old behavior via about:config setting "network.cookie.cookieBehavior" to 1, which should really not be the permanent solution for this issue. Dunno why this is not getting proper attention, maybe it would delay FF2. Who knows, bad decision anyway.

#20 Re: Re: Huge concern

by Gnerma

Sunday October 8th, 2006 7:56 AM

Reply to this message

If you read the comments in that bug, you'll see the explanation for the removal of this option. Although I find myself asking, "Just because this can easily be worked around, does that mean that the workaround is always employed?" I'd liken it to somebody turning off a firewall because they know there is a way somebody can get past it, or somebody not wearing armor into battle because a strong sword thrust could go through a seam, or not wearing a seatbelt because it won't guarantee that you'll survive a crash. I could go on..

#23 How to fix ...

by johann_p

Monday October 9th, 2006 11:06 AM

Reply to this message

The obvious way to fix this is to also (optionally) allow users to disable Javascript that is not from the original host -- this way the workaround is not any more possible and that option would be very useful by itself.

I just wonder how other browsers that do have the option of disabling cookies not from the original host (Konqueror, Opera) work.

#25 Re: How to fix ...

by leafdigital

Tuesday October 10th, 2006 2:40 AM

Reply to this message

Same way as Firefox used to i.e. not very well.

--sam

#31 eWeek: "Firefox 2.0 RC2 Is a Step Backward?"

by roseman

Tuesday October 10th, 2006 11:04 AM

Reply to this message

eWeek has an article about FF-RC2, mentioning a few changes that are, umm, "negative" (in their view): <http://www.eweek.com/arti…le2/0,1895,2026597,00.asp>

article starts out: "Firefox 2.0 RC2 Is a Step Backward?" and then: "Review: eWEEK Labs was disappointed to find that a couple of well-liked search and cookie options have been changed in RC2..." (then article continues from there).

These changes are not show-stoppers for me, but it is discouraging to see good features go away :(

#34 Re: eWeek: "Firefox 2.0 RC2 Is a Step Backward?"

by Gnerma

Wednesday October 11th, 2006 2:32 AM

Reply to this message

I believe this article serves as a nice little preview of what the general response to the Quick bar / Find bar debacle will be if 2.0 ships with it as is. To your average users, who by the way rarely ever use keyboard shortcuts, all the change will bring to mind is, "why the heck did they remove the find next/previous buttons making this key feature I love useless?" A few will end up at places like Mozillazine asking how to "fix" it, but most people will just feel helpless and betrayed with no idea how to make FAYT useful again.

#32 Yep, the Firefox 2.0 team really dropped the ball

by deepgloat

Tuesday October 10th, 2006 12:32 PM

Reply to this message

Yep, the Firefox 2.0 team really dropped the ball on the third-party cookie issue. Any workaround that requires Joe Sixpack to venture into the user-hostile about:config screen is A Bad Thing.

#35 Re: Yep, the Firefox 2.0 team really dropped the b

by leafdigital

Wednesday October 11th, 2006 5:15 AM

Reply to this message

I don't know, it does seem a bit of an unhelpful feature if it's so easy to work around. Then you're really only deceiving the user that the browser can reject third-party cookies, when it fact it can't, unless the evil organisation trying to set the cookies is particularly stupid.

On the other hand, removing the options from Find as you Type is just silly. That's on purpose? I'd assumed it was a bug. What's the point of removing those options? There weren't too many and now that bar is just blank; how does that help anyone? It doesn't particularly affect me as I always pressed F3 anyway but I come from the user interface school where making core features visible is a good idea...

--sam

#33 Close tab button

by dodgeandburn

Tuesday October 10th, 2006 2:00 PM

Reply to this message

I wish the Close tab button at the far right hadn't been removed. There's a few times I have closed the wrong tab by accident. But by using the close tab button at the far right, you're sure to close the current tab.

Please bring back the global close tab button!!!

Thanks

#36 No, don't.

by leafdigital

Wednesday October 11th, 2006 5:20 AM

Reply to this message

The previous interface was bizarre - you clicked nowhere near the tab you wanted to close. What's next, shall we move the X button on application windows to the top right of the screen and make it only work for the current window? If the operating system worked that way, then the X button at far right would make sense. But none of them do and it didn't.

I've never closed the wrong tab with the new system, but two or three times did close the wrong one with the old system (I wanted to close the far-right tab and saw an X near it and subconsciously thought it would work, presumably because I also use several other tabbed programs, all of which place their close buttons on the tabs).

On the plus side, if you do have any issues while getting used to the new system, it's now possible to get back any tabs you accidentally close. Just go to History / Recently closed tabs.

--sam

#43 Re: Close tab button

by hhh

Thursday October 12th, 2006 10:59 AM

Reply to this message

There is a hidden preference for this. In about:config, right-click a preference and choose New>Integer. Copy/paste browser.tabs.closeButtons into the field, then set the value to 3.

#37 Removing the options on find as you type is stupid

by johann_p

Wednesday October 11th, 2006 8:20 AM

Reply to this message

Must be a bug or can anyone actually come up with a reasonable argument why it is an improvement to remove the buttons that are present on the bar when one uses the "Find in this page" option (either via the menu or via the keyboard shortcut).

The argument constantly brought forward why the option for acception cookies from the original host only was removed is not that good either: first, at least a lot of cookies are still filtered that way, so deleting the rest would be much easier. Second, one could warn for now and try to prevent the workaround -- the best way to do this IMO would be to simply also have an option to only allow Javascript from the original host only. That would solve the cookie workaround problem AND would prevent a lot of totally useless and intrusive Javascript from being run (Third party Javascript code usualy is just there for ads, stats and other and maybe even worse unwanted crap).

#38 Blank horizontal bar above menu bar.

by dodgeandburn

Wednesday October 11th, 2006 9:56 AM

Reply to this message

For some reason I'm getting a blank horizontal bar above the menu bar and it's the thickness of the menu bar. It shows up after a while and won't go away until I restart firefox. I don't remember if this is a version 2 only issue or not. But it's annoying. I'm guessing that it might be an old theme that left something in the configuration file.

#39 User interface - earlier feature now missing

by alieninvader <alieninvader@earthlink.net>

Wednesday October 11th, 2006 12:49 PM

Reply to this message

In Firefox 1.7.x and prior, you could hold down the mouse button on a hyperlink and a menu would pop up allowing you to open the link in a separate window or tab.

With 2.0 RC2, this is only available if you click 'ctrl' when clicking the mouse. It's an added step that's a bit annoying.

If any developers are listening, please put this back in!

Thanks- Steve

#42 Re: User interface - earlier feature now missing

by BenoitRen

Thursday October 12th, 2006 10:43 AM

Reply to this message

There was no Firefox 1.7.x. You're confusing it with the Mozilla Application Suite. Stop abusing its name.

#44 Two button mouse

by wayneo

Friday October 13th, 2006 4:19 AM

Reply to this message

I imagine this is standard for mac. I still don't understand how you can use a one button mouse. get a two button mouse like everyone else and just right click.

#40 Clarifying the prev msg

by alieninvader <alieninvader@earthlink.net>

Wednesday October 11th, 2006 12:56 PM

Reply to this message

Message 39 above refers to the Mac OSX version. If this is the wrong forum to post on, let me know which forum is correct. I hate to see this as a feature request since it has been a feature already. (or did someone declare it a bug ;-)

#49 Re: Re: Re: window.open()

by markob <markob_mcs@hotmail.com>

Sunday October 15th, 2006 6:01 PM

Reply to this message

To add a key 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 events 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.

#50 Closing the last tab doesn't close the window

by polyfade

Sunday October 15th, 2006 6:06 PM

Reply to this message

In prior releases to FF RC2, if I had tabs always showing, after closing the last tab, it would always close the window. Now, it doesn't. It's irritating since I assign keyboard shortcuts to my mouse buttons. Is there something in the about:config that needs to be set so it behaves like before?

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1) Gecko/20061003 Firefox/2.0

#51 Is Firefox RC2 spying on me?

by marknelkin

Monday October 16th, 2006 1:26 PM

Reply to this message

Recently when I run spybot, I find a lot of "spyware" from Firefox default tracking cookie. It used to be only one or two, but now it is 28. When I uninstalled talkback, this went away. Should I be concerned about these tracking cookies? Does Mozilla know more about how I use my computer than I want it to know?

#52 Is Firefox RC2 spying on me?

by marknelkin

Monday October 16th, 2006 1:30 PM

Reply to this message

Recently when I run spybot, I find a lot of "spyware" from Firefox default tracking cookie. It used to be only one or two, but now it is 28. When I uninstalled talkback, this went away. Should I be concerned about these tracking cookies? Does Mozilla know more about how I use my computer than I want it to know?

#53 RC3 is out, has the same problem as RC2 for me

by meteo

Tuesday October 17th, 2006 6:07 AM

Reply to this message

Can it be that Mozillazine is behind Techcrunch in Mozilla reporting? <http://www.techcrunch.com…p-heres-what-to-look-for/>

My RC2 started having weird problems after a week of flawless usage. There seemed to be 100% processor throttling for 3 seconds in regular ~ 20 second intervals which completely froze the browser. When I downgraded to 1.5 and replaced the profile with the old version, problem dissapeared and reappeared when I installed RC3 on top of this old profile. Anyone else noticed this?