The Official Win32 20040705 [Br/Tr] builds are out.

Discussion about official Mozilla Firefox builds
User avatar
Peter(6)
Posts: 13011
Joined: September 4th, 2003, 1:26 am
Location: Maassluis, The Netherlands

The Official Win32 20040705 [Br/Tr] builds are out.

Post by Peter(6) »

The Official Win32 ..... builds are out , Firefox (RSS feed) ***Changed URL, bookmark this one***
The Official Win32 2004-07-05 [Aviary Branch] build yet out.
The Official Win32 2004-07-05 [Trunk] is out.


The previous Official Win32 build was 2004-07-04 BRANCH || 2004-07-04 TRUNK

The latest nightly general directories: Official Branch || Official Trunk] || Unofficial Branch/Trunk

Firefox 0.9.1 Releasenotes || Extensions || Themes

If you find problems/bugs:
  1. Post them in this thread
  2. Properly describe the problem
  3. Include the url where you have the problem (if this is the case)
  4. Include the "about mozilla firefox" information (under the help button)
  5. Installer build or .zip version?
  6. Did you completely erase the Firefox directory first?
  7. Does a new profile fix the problem?
  8. Include the list of extensions you have installed (preferably none to start with)
This makes it a lot easier for others to duplicate your problem.

Last update: 2004-07-05 10:32PDT = 17:32UTC

Fixes: OS in []
  1. TRUNK:#244334Text Zoom Ctrl++ broken [Win]
  2. TRUNK:#234686fix scaling of images in response to min/max-width/height [All]
  3. TRUNK:#17602Arrow keys should change radio buttons, not Tab [All]
  4. TRUNK:#249416file input controls display incorrectly in quirks mode [All]
  5. TRUNK:#249665textarea does not recognize newlines [Lin]
  6. TRUNK:#249810Reduce allocations by nsViewManager [Lin]
  7. TRUNK:SVG:#245408'position' shouldn't apply to SVG elements [Lin]
  8. TRUNK:SVG:#236853Crash when SVG text element is placed inside XUL template [Lin]

Patched but not completely fixed:
  1. none

Regressions/confirmed/annoying bugs:
Make sure you vote for bugs that you suffer from.
Do NOT vote for bugs you don't see on your system.

  1. BOTH:#237766background-image gets painted double on link hover.[Win]
  2. BOTH:#246754Theme InstallTrigger links don't work with HTTP redirects.
  3. BOTH:#247713Expand/collapse widget still present for bookmark folders even if there's no subfolders in Firefox's 2-pane Bookmark Manager [Win]
  4. BOTH:#247960The 2 panes of bookmarkmanager do not interact [Win]
  5. BRANCH:#134260[meta] Dynamic theme switching (change skin) [All]
  6. BRANCH:#221482Bookmarks toolbar temporarily cleared when clicking "Restore Default Set" in customize mode [All](patch in review)
  7. BRANCH:#225281background problem behind text on the "Install Complete" page
  8. BRANCH:#232707Right-click context menu for toolbar bookmarks broken after customizing navigation toolbar icons.[Win](patch in review)
  9. BRANCH:#244888Failed Theme/Extension downloads should display download error. [Win]
  10. BRANCH:#245053Profilemanager crashes when you try to delete a profile [Win]
  11. BRANCH:#245327theme switch clears all tabs, disables their history, can't close these tabs [All]
  12. BRANCH:#246012Crash when pressing f6 on page with iframe and applied custom CSS style [@ nsEventStateManager::IsIFrameDoc ]
  13. BRANCH:#246078Firefox does a lousy job of making itself the default browser[Win].(Workaround see comment #26)
  14. BRANCH:#246417Statusbar/Advanced Options software updater fails even if extension update exists.[Win]
  15. BRANCH:#246756Firefox bookmarks do not lead to u.m.o for themes extensions. (patch in review)
  16. BRANCH:#248423config.trim_on_minimize no longer works [Win]
  17. BRANCH:#249819login button doesn't work [Win]
  18. TRUNK:#000000 the new EM does not work yet.

Firefox 1.0 Beta (July) and 1.0 Milestone (September) bugstatus for ALL operating systems: (+/- are changes compared to the previous nightly build)

Bugs nominated to block Firefox 1.0 = 42 ( +1 )
Bugs accepted to block Firefox 1.0 = 191 ( -1 )
Bugs blocking Firefox 1.0 and FIXED = 31 ( +1 )

this message will be edited if there is any update.
Last edited by Peter(6) on July 5th, 2004, 10:43 am, edited 10 times in total.
nightly build threads 20040225 (FF 0.8.0+) - 20120331 (FF14a)
Zaagmans
Posts: 42
Joined: June 6th, 2004, 12:47 pm
Location: Wilp (GLD), The Netherlands
Contact:

Post by Zaagmans »

[off-topic] jij bent er snel bij Peter! ;-) [/off-topic]
User avatar
Peter(6)
Posts: 13011
Joined: September 4th, 2003, 1:26 am
Location: Maassluis, The Netherlands

Post by Peter(6) »

Zaagmans wrote:[off-topic] jij bent er snel bij Peter! ;-) [/off-topic]

[off]Te druk op het werk (veel mensen op vakantie), dan maar vast 'savonds inkloppen ;-)[/off]
nightly build threads 20040225 (FF 0.8.0+) - 20120331 (FF14a)
disabled
Posts: 18
Joined: June 30th, 2004, 3:49 pm

Post by disabled »

Peter(6) wrote:I found a problem in your list, some bugs are blocking 1.0 and 1.0RC, making them appear in both lists


I did not see this as a problem. That's just the way the flags are set. However, if you would like to have a total bug count of all bugs that have either the <code>blocking-aviary1.0RC1</code> flag or the <code>blocking-aviary1.0</code> flag (or both) set, try the above links (Firefox 1.0-any). They should do the trick.

Actually, I've found some problems in your lists ;-)

First, it looks like the <code>bug_status=UNCONFIRMED,NEW,ASSIGNED,REOPENED</code> part in your URLs has the wrong format. I think what you want is <code>bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED</code>. Otherwise the Edit Search feature won't work.

Also, <code>bug_status=RESOLVED,FIXED</code> does not work. The resulting list contains INVALID, WONTFIX and DUPLICATE bugs while omitting those that are VERIFIED. Try <code>bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED</code>.
phrozenfire
Posts: 16
Joined: May 24th, 2004, 9:32 am

Re: The Official Win32 20040705 [Br/Tr] builds are not yet o

Post by phrozenfire »

Peter(6) wrote:The latest nighly general directories: Official Branch || Official Trunk] || Unofficial Branch/Trunk


Not a big deal, but you typoed nightly.
disabled
Posts: 18
Joined: June 30th, 2004, 3:49 pm

Post by disabled »



No, the first three links (Firefox 1.0-any) would be enough.
They catch all bugs blocking (or nominated to block) Firefox 1.0RC1 or Firefox 1.0final or both.

(It all really depends on the reasons for the introduction of the new blocking-aviary1.0RC1 flag and what kind of granularity you want to have when listing this kind of bug statistics.)
User avatar
Peter(6)
Posts: 13011
Joined: September 4th, 2003, 1:26 am
Location: Maassluis, The Netherlands

Post by Peter(6) »

I'll use the first 3 , I assume Ben will push 99% of them to block 1 of the 3 RC's anyway.
Introducing RC1 would only force me to introduce RC2 and 3 in a later phase, making it way too complex to read and/or maintain/
Thanks a lot for the help.
nightly build threads 20040225 (FF 0.8.0+) - 20120331 (FF14a)
Krule
Posts: 66
Joined: February 11th, 2004, 3:55 pm
Location: Montreal, QC
Contact:

Post by Krule »

Should we be using the trunk or branch now...this whole...trunk/branch issue is confusing for my little head :p
User avatar
Peter(6)
Posts: 13011
Joined: September 4th, 2003, 1:26 am
Location: Maassluis, The Netherlands

Post by Peter(6) »

Branch :-)
nightly build threads 20040225 (FF 0.8.0+) - 20120331 (FF14a)
hussam
Posts: 616
Joined: August 22nd, 2003, 11:49 am
Contact:

Post by hussam »

I have a question. I hope one of the developers is actually reading this although I seriously doubt it.

bug 221482 has a patch and it has been approved.

------- Additional Comment #25 From Mike Shaver 2004-07-01 08:04 PDT [reply] -------

(From update of attachment 151847)
Bingo. r=shaver, please land on the aviary branch.

http://bugzilla.mozilla.org/show_bug.cgi?id=221482
When will it exactly land?
User avatar
Peter(6)
Posts: 13011
Joined: September 4th, 2003, 1:26 am
Location: Maassluis, The Netherlands

Post by Peter(6) »

bugs (Ben) approved it so it'll get in one day ;-)
nightly build threads 20040225 (FF 0.8.0+) - 20120331 (FF14a)
djl47
Posts: 253
Joined: October 9th, 2003, 12:49 am
Location: California

Post by djl47 »

Peter(6) wrote:I'll use the first 3 , I assume Ben will push 99% of them to block 1 of the 3 RC's anyway.
Introducing RC1 would only force me to introduce RC2 and 3 in a later phase, making it way too complex to read and/or maintain/
Thanks a lot for the help.


I think that is fine for this list. It would be cool if the additional searches could be squirreled away somewhere (Perhaps I'll add them to my elcheapo notepad generated web page :-)

There's a typo in the branch build link. I don't think you've seen it yet.

The grim reality of 192 bugs blocking Firefox 1.0 is that the numbers are against all of these being fixed within the current release schedule. If the developers average a fix of three blockers a day all of these could be fixed by September when Firefox is currently schedued to be released.

http://www.mozilla.org/projects/firefox/roadmap.html
User avatar
Peter(6)
Posts: 13011
Joined: September 4th, 2003, 1:26 am
Location: Maassluis, The Netherlands

Post by Peter(6) »

djl47 wrote:The grim reality of 192 bugs blocking Firefox 1.0 is that the numbers are against all of these being fixed within the current release schedule. If the developers average a fix of three blockers a day all of these could be fixed by September when Firefox is currently schedued to be released.
http://www.mozilla.org/projects/firefox/roadmap.html
Well, I don't think you're right and actually hope you are wrong. It would be a huge mistake to pull the same trick as with 0.9 (and 0.9.1 for that matter) , releasing it on date, no matter how finished/unfinished it is. My opinion is that a blocker should block the release unless the problem is unsolvable without introducing security issues. If 1.0 is being advertised as rockstable (and the best there is) then there isn't much room for compromise, otherwise it would just be another beta (like 0.9/0.9.1).
nightly build threads 20040225 (FF 0.8.0+) - 20120331 (FF14a)
Post Reply