Meet Firefox 4.0.1

[ad!k1337]

Wow, a candidate for a Beta :rolleyes: When are they going to release the candidate to the candidate of the Beta? :laugh:

Troll alert !!! :lmao:

[bogas04]

Wow, a candidate for a Beta :rolleyes: When are they going to release the candidate to the candidate of the Beta? :laugh:

• Code Freeze: 11/04
• Builds Start: 11/04
• QA: 11/04 - 11/09 (estimate)
  • Smoketests and BFTs using Mozmill: (1 person)
  • Manual smoketests, BFT areas, and Other OS Spot Checks: 11/04-11/09 (3 people)
  • Testday: 11/05 (3 people monitoring)
  • Accessibility: On-going (1 person)
  • Top Sites Functionality and Page Load Testing: Before 11/09 (1 people)
  • Updates checks: Before 11/09 (1 person)
    • Manual spot checks as necessary

Seems like tuesday is the day (in Indian system , it would be called 9/11)

[bogas04]

After seeing this , i think why are we still using flash? Try scrolling while its playing , its like , plain text! Worth a try!

[torrentthief]

Looks like beta 8 will be quite a while away, 84 blockers for it: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking2.0:beta8+

[bogas04]

Looks like beta 8 will be quite a while away, 84 blockers for it: https://bugzilla.moz...cking2.0:beta8+

Fennec Beta 2 is out , and beta 7 is done , so they can work on beta 8 easily now

[macmax]

Firefox 4.0b8pre 0/11/2010

V8 - 3421

Sunspider 0.9.1 - 253.7ms +/- 6.6%

Kraken - 6801.7ms +/- 0.7%

Seems to get better :)

[iwod]

Although i have been using Minefield on my very old Office PC and only Beta 6 on my home PC. Beta 7 makes using Firefox on my Home PC enjoyable again.

For now, the speed difference is no longer substantial between Firefox and Opera / Chrome. Page Rendering and JS are still little slower. But i cant live with that, for all the great extensions and awesome bar.

[yowanvista]

Beta 7 still not released

[Kirkburn]

Beta 7 still not released

No, it's not. The schedule was already posted a few posts back.

Wait until approx Tuesday, or risk installing the build1 candidate.

[gahbmwM5]

Hello,

As I just D/L and installed the FF4.0b7 RC1 build, but was curious as I wanted to update my sig @mozillaZine Forums--->it use to be:

Mozilla/5.0 (Windows NT 6.0; rv:2.0b6) Gecko/20100101 Firefox/4.0b6

However now when I go to help--->About

Uploaded with ImageShack.us

Any ideas where a 'string would be'...? lol

[crispkreme]

Any ideas where a 'string would be'...? lol

It's stupid that they removed the string from the about box, but you can still see it by typing

about: in the urlbar.

Build identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101106 Firefox/4.0b8pre

[gahbmwM5]

It's stupid that they removed the string from the about box, but you can still see it by typing

about: in the urlbar.

Build identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101106 Firefox/4.0b8pre

Thanks crispkreme...:) It was getting me kind of annoyed on this nice Saturday afternoon...lol! I could not find it anywhere...

[Kirkburn]

Note: the build strings in main releases (beta, final) will always show Gecko/20100101 now, to avoid 'fingerprinting'.

[gahbmwM5]

Note: the build strings in main releases (beta, final) will always show Gecko/20100101 now, to avoid 'fingerprinting'.

You answered my next question...lol

As I was wondering why the Beta 4.0 builds showed Gecko/20100101, with (IIRC) Beta 1, 2, 3, 4, 5, and 6..

Thanks Kirkburn

[The_Decryptor Veteran]

Note: the build strings in main releases (beta, final) will always show Gecko/20100101 now, to avoid 'fingerprinting'.

People were using it as a version identifier for some strange reason, random sites would break every year since they didn't expect the year increase of nightly builds and such.

By freezing it on a set date, they'll force those people to either update their code, or make it never have an issue again (unless they then remove the fake date which I think is the general plan)

[primexx]

People were using it as a version identifier for some strange reason, random sites would break every year since they didn't expect the year increase of nightly builds and such.

By freezing it on a set date, they'll force those people to either update their code, or make it never have an issue again (unless they then remove the fake date which I think is the general plan)

hmm shouldn't they just do it in one go rather than risking two potential breakages?

[The_Decryptor Veteran]

I think it's a transition thing, but it might end up never being removed (They've just removed the "strong encryption" flag back from the Netscape 4 era)

[Kirkburn]

More info on the UA changes here: http://hacks.mozilla.org/2010/09/final-user-agent-string-for-firefox-4/

The fingerprinting was also a security issue I believe - it lets you target people with acccurate security-related information.

[aznkid25]

Edit: Wrong thread.

[chrisdoland]

I think they should remove the string SOOoon! I hear it's really unhealthy to leave it in along time.

[crispkreme]

Taken from buildnotes page. Here is what is left to be done before beta 7.

Final checks before push

Virus check

Update Bouncer

Push to mirrors

• Wait for email from driver before continuing

Final verify

Push snippets to beta channel

Remove index.html files

Release

[flexkeyboard]

It has been almost two months since the last Beta. Very excited for this beta 7. Can't wait! :cool:

[The_Decryptor Veteran]

Will Beta 7 be the first one with JaegerMonkey? I've been using the nightlies so I haven't kept track of the milestones that well.

[Frylock86]

Beta 7 still not released

Wednesday ;)

[Sub_Zero_Alchemist]

Will Beta 7 be the first one with JaegerMonkey? I've been using the nightlies so I haven't kept track of the milestones that well.

Yup.. if no blockers are found. Beta 7 should be released within the next couple of days. looking forward to beta 7 myself.