Latest Nightly Discussion: firefox-3.0a1.en-US...

[Michael Genzuk]

In today's Nightly builds I saw firefox-3.0a1.en-US... for the first time. Can anyone tell me what this version is about?

[Scanorama]

#330528[Firefox:Build Config]- bump Firefox version on trunk to 3.0a1 [All]

[pal-moz]

http://wiki.mozilla.org/Global:1.9_Trun ... ranch_Plan

[James]

From The Official Win32 20060407 [Trunk] build is out. thread.

Is where the above #330528[Firefox:Build Config]- bump Firefox version on trunk to 3.0a1 [All] is from.

There is also Bug#330533 - create new "About Firefox" graphics for Bon Echo and trunk and Bug#308973 - Rebrand Firefox trunk and 1.8 branch builds to avoid confusion

[greenknight]

Basically, the only difference is that extensions suddenly become incompatible, you need to bump their maxversions again.

[angelica]

Basically, the only difference is that extensions suddenly become incompatible, you need to bump their maxversions again.

yes, sure..

so, no real differences?

and another thing..where from do I know the name of the build? I mean, Pacifica, Cairo, BonEcho and the likes..

[pikaunforgiven]

about:buildconfig will tell you some of it, pacifica is a build machine, you find that out when you download from one of the links in peter's posts. any build that is 2.0a1 is bon echo so thats kinda a no brainer.

[ehume]

The MR Tech Local Install extension will let you tell Fx to ignore the maxversion. Just download the extension's xpi file and use Local Intall's "Install" button to install from a folder on your hard drive.

[greenknight]

In spite of what I said in a previous post, I don't manually bump my extensions. I use the Nightly Tester Tools extension to make them compatible. After this update, though, the extensions could not be enabled even after they were made compatible. Fortunately, I'd seen this before and knew what to do; if you have this problem, simply re-install the browser.

[SurlyDuff]

In spite of what I said in a previous post, I don't manually bump my extensions. I use the Nightly Tester Tools extension to make them compatible. After this update, though, the extensions could not be enabled even after they were made compatible. Fortunately, I'd seen this before and knew what to do; if you have this problem, simply re-install the browser.

Odd, I was easily able to bump my extensions with Nightly Tester Tools...maybe it was because I was using version 1.0rc1(before 1.0 came out):\

[EagleClaw]

This new build is really fast on my system, more so than anyone I can remember trying in some time.

Adblock not working is the major drawback for me not using this full time.

How soon can one expect a new version of Adblock to work with this??



thanks

[Harald.L]

How soon can one expect a new version of Adblock to work with this??

What's the problem? I'm running AdBlock Plus 0.5.11.3 (the version from mcm_ham) available from http://forums.mozillazine.org/viewtopic.php?t=266291 and made compatible with 3.0a1 by nightly tester tools 1.0 with no problems at all!

Harald
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9a1) Gecko/20060412 Firefox/3.0a1 ID:2006041205

[lastman]

How come none of my extension work on Fx 2 or 3 even though i have enabled and made them compatable with Nightly Tester Tools?

Can someone help me? I have been looking to upgrade Fx but the extension just dont work!

[the-edmeister]

How come none of my extension work on Fx 2 or 3 ...

That's 2.0a1 and 3.0a1. You must not be using NTT correctly if you can't get any extensions to work in either version.

This thread discusses all the extensions other users have gotten to work in BonEcho (2.0a1) by modding the maxVersion, which is basically what NTT does to get then to install.
http://forums.mozillazine.org/viewtopic.php?t=396126

Ed

[lastman]

Hmm, its a totally different problem i think.

I removed my current profile directory or the whole Mozilla directory in Application Data folder and ran 3.0a1 with a completely new profile. I installed NTT and i installed a extension which didnt work before. But now it does, with the new profile the extension worked. Whats happening here? Do i have to create a new profile and install all the extensions again?