• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Firefox 2.0 final is out

Page 5 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Originally posted by: SonnyDaze
Originally posted by: thehstrybean
Normally, I'd take the time to write up a more in-depth explanation, but since my schedule is... uh... "hectic" right now, I'll just say this:

1. No, we have. Not. Released. Firefox. 2. Yet.
2. When people link to bits directly on a random FTP mirror, they're doing a number of people harm including, quite possibly, themselves:
* Digg and Reddit posts linking to direct FTP mirrors could be costing the operators of those mirrors hundreds to thousands of dollars in bandwidth bills, or may cause them to crash by linking directly to them. This could cause them to "un-volunteer" their services as a mirror, making it even harder to obtain Firefox on release days.
* People posting direct link to FTP mirrors don't know if that mirror is a member of the Mozilla FTP Mirror Farm, or some random, unverified mirror. We work hard to verify that the mirrors in our farm are serving the same bits we released, and we cannot make the same claim about other mirrors that aren't part of our farm. When using direct FTP links to random mirrors, users run the risk of downloading bits that have not been checked to ensure they do not contain a virus or trojan.
* "That's ok," you say: "I link directly to ftp.mozilla.org!" That can be even worse! Killing the project's FTP server does not help anyone, least of all people trying to obtain Firefox builds. And it makes for a grumpy IT group. And nobody wants grumpy IT groups. Especially a day before a release.
3. Linking directly to builds hinders our ability to remove/retract bits that we may have to remove for some reason. While this may not seem like a big deal, it becomes a problem when supporting users, one of our most important values. If, let's say, we pull a locale, due to a stop-ship bug?and yes, this is not a hypothetical?then users who've (pre-)downloaded that build will not receive valuable security updates for those builds. The counterargument to this is "Well, you should provide updates for everything you've ever offered on your FTP site." If we did this, we'd be spending valuable (and über-constrained) Build Team and QA resources generating updates and testing them for builds that weren't the final bits, and were never "released" as such.
4. Posting links before we release may point people to an incomplete FTP areas or mirrors. I haven't finished posting the source tarball, for instance. Will it happen before we release? Yes. Will there be unnecessary confusion from the open source community, wondering where this deliverable is? If you post links to an FTP site with the builds, yes.
5. Most articles have an unerring ability to link to the wrong thing. Slashdot's front page, for instance, currently links to the Windows British English build. I cringe at the thought of the community having to waste time while we're finishing things up with IRC, blog, and Bugzilla chatter asking "I got my build from Slashdot; why did you guys spell behaviour wrong?" And where are Slashdotters wanting uhh... you know... Linux builds supposed to get them? It's unclear from the article that directly links to an .exe for one [correct for one country, but mostly-wrong for everyone else] locale.
6. User experience can be degraded, leaving a bad taste in people's mouth: Firefox 2 has a number of components that use live content on websites. The whole community has been doing a lot of work to refresh, update, and translate this content, and parts of it are still coming together for the release. When you download a build, there could be various content, including certain parts of help, that are not yet ready. When you tell your friends to go download Firefox 2 before we announce it's ready, you're subjecting them to a degraded user experience, which could push them to go back to... "other browsers."

Now, before you suggest it, it's not as easy as putting in .htaccess restrictions, or setting the permissions on the files so people can't download them. The nitty-gritty details are in the newsgroups.

So please... just remember: "Preed the Release Engineer says: friends don't let friends download Firefox before it's released."

We know everyone's excited for the 2.0 release. We are too. But give us 24 hours, so we can make sure that your first experience with Firefox 2.0 is befitting of everyone's hard work on this major release.

I promise it's worth the wait.

Text
Click to expand...

Might be interested in this....😕
Click to expand...

Tryin to get that discussion started in that thread. I think it's weird that this happened...
 
I see firefox copied the "X" in each tab from Opera 😕 First they copy tabs... now they copy the "X"... what next, are they going to copy the opera logo?

 
Originally posted by: schneiderguy
I see firefox copied the "X" in each tab from Opera 😕 First they copy tabs... now they copy the "X"... what next, are they going to copy the opera logo?
Click to expand...

This- you.. I mean- headache now.
 
Originally posted by: schneiderguy
I see firefox copied the "X" in each tab from Opera 😕 First they copy tabs... now they copy the "X"... what next, are they going to copy the opera logo?
Click to expand...

Tabs was invented by a IE shell browser (Netcaptor if I recalled) and had nothing to do with Opera or Firefox.

The close button on the tabs can be removed in about:config for those that don't like it.
 
Originally posted by: schneiderguy
I see firefox copied the "X" in each tab from Opera 😕 First they copy tabs... now they copy the "X"... what next, are they going to copy the opera logo?
Click to expand...

Tab mix has had the "x" in the tabs since it was first released...
 
sweeeeet
downloaded it yesterday and the first thing i noticed, apart from the ugly "go" button that you can't remove is the inline spellchecker which is kinda cool but annoying at the same time!
 
I'm having problems with pop ups or links that open a new window freezing the browser, requiring me to do an "End Task" on it. Never had the problem with 1.5.0.7.
 
Originally posted by: NFS4
I'm having problems with pop ups or links that open a new window freezing the browser, requiring me to do an "End Task" on it. Never had the problem with 1.5.0.7.
Click to expand...

Same here. I got tired of it and am back to 1.5.0.7.
 
Originally posted by: johnjbruin
Originally posted by: NFS4
I'm having problems with pop ups or links that open a new window freezing the browser, requiring me to do an "End Task" on it. Never had the problem with 1.5.0.7.
Click to expand...

Same here. I got tired of it and am back to 1.5.0.7.
Click to expand...

I wonder if it could be an extension compatibility problem. I'm using Nightly Tester Tools to enable my incompatible extensions.
 
Originally posted by: 13Gigatons
Tabs was invented by a IE shell browser (Netcaptor if I recalled) and had nothing to do with Opera or Firefox.
Click to expand...
Opera has always had an MDI. The adoption of a TDI was a rather small revision starting late v 3.x/early 4.x of Opera.

The actual pioneer was InternetWorks, which came several years prior to NetCaptor.
 
Originally posted by: NFS4
Originally posted by: johnjbruin
Originally posted by: NFS4
I'm having problems with pop ups or links that open a new window freezing the browser, requiring me to do an "End Task" on it. Never had the problem with 1.5.0.7.
Click to expand...

Same here. I got tired of it and am back to 1.5.0.7.
Click to expand...

I wonder if it could be an extension compatibility problem. I'm using Nightly Tester Tools to enable my incompatible extensions.
Click to expand...

Probably. I have no problems with FF 2.0, but then again I haven't enabled any incompatable extensions.
 
Originally posted by: mrSHEiK124
Originally posted by: SoulAssassin
After you upgrade to 2.0 you HAVE to try the Noia 2.0 theme...seriously kicks butt.

<a target=_blank class=ftalternatingbarlinklarge href="https://addons.mozilla.org/firefox/72/"><a target=_blank class=ftalternatingbarlinklarge href="https://addons.mozilla.org/firefox/72/">https://addons.mozilla.org/firefox/72/</a></a>
Click to expand...

I don't understand the obsession with the Noia theme, I installed it and thought it was hideous, both now with FF 2.0 and at least a year earlier when a friend showed it to me.
Click to expand...

I have to agree, I've not seen a better FF theme than the default. In fact, I like the old pre-2.0 default better than the current one, as well.

The Noia is hideous. I have no idea why it is so popular.
 
Originally posted by: Shawn
Originally posted by: NFS4
Originally posted by: johnjbruin
Originally posted by: NFS4
I'm having problems with pop ups or links that open a new window freezing the browser, requiring me to do an "End Task" on it. Never had the problem with 1.5.0.7.
Click to expand...

Same here. I got tired of it and am back to 1.5.0.7.
Click to expand...

I wonder if it could be an extension compatibility problem. I'm using Nightly Tester Tools to enable my incompatible extensions.
Click to expand...

Probably. I have no problems with FF 2.0, but then again I haven't enabled any incompatable extensions.
Click to expand...

Well, I reinstalled FF2.0 and left out the disabled extensions. Still get lockups. Oh well, back to 1.5.0.7 for me.
 
Originally posted by: NFS4
Originally posted by: johnjbruin
Originally posted by: NFS4
I'm having problems with pop ups or links that open a new window freezing the browser, requiring me to do an "End Task" on it. Never had the problem with 1.5.0.7.
Click to expand...

Same here. I got tired of it and am back to 1.5.0.7.
Click to expand...

I wonder if it could be an extension compatibility problem. I'm using Nightly Tester Tools to enable my incompatible extensions.
Click to expand...

You're a lifesaver, I was dying without Fingerfox and thus without my fingerprint reader.
 
click tools then options, why are the top pictures screwed up (main, feeds, and security)? and where do you go now to configure extensions and themes?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top