Firefox 1.5 Bug Report

[supernova_00]

This graph is to show the number of bugs either fixed, blocking or nominated to block the 1.5 release of Firefox. Firefox 1.5 is currently scheduled for release in the Fall. The links below are queries showing the bugs that block, requesting to block or fixed for 1.5. I will update the graph once a day to show the progress of each day.

Queries used:

Bugs accepted to block 1.5

Bugs nominated to block 1.5

Fixed 1.5 Blockers

-----

Firefox 1.5 Roadmap

-----

"New Features" that should be included in Firefox 1.5

(Green=Already in the nightlys---will be in 1.5 | Orange=Patched but not fully fixed or turned on by default)

1) 'Sanitize Settings' which automatically removes privacy information with a keyboard shortcut or when closing firefox. (Screenshot)

2) Options Window UI Update (Video | Screenshots)

3) New Cookie Controls per site (Screenshot)

4) Extension Manager upgrades:

• Command Line Installation/Uninstallation
  
• Server-Side GUID Blacklist
  
• Enhanced Global Registration
  

5) Mac Profile Migrators for:

• Apple Safari
  
• Mozilla Camino
  
• Microsoft Internet Explorer 5.x
  
• Omniweb 5
  

6) Searchable download actions manager (now with integrated full page plugin support)

7) Possible Accessibilites options (ScreenReader support is being worked on, not sure if its enabled or not)

8) Drag-and-drop reordering of tabs

9) Instant Back and forward navigation

10) SVG Support

11) Support for Always Storing Cache on Local Filesystem

12) Provide utility for incremental download (Key part for patches instead of full releases for updates)

13) Reporter Tool (To report broken websites)

14) <canvas>

Edited October 13, 2005 by supernova_00

[saxondale.]

Once again, thanks for that supernova

[supernova_00]

Just wanted to add that I got the idea from sensemann's towards 1.0 thread (on mozillazine forums). He hasn't been around for a while so I started a new thread for 1.1 on neowin and mozillazine. I think its fun to watch and keep everyone updated on the progress towards 1.1 and gives a good idea on when a release will be released based on how many blockers are left. The flags for blocking-aviary1.1 was created last week and the devs have not gone through the list yet to approve which ones will block expect for the two so far. Next week the devs are going to go through the list. So this graph will be looking good next week once things get sorted out and blockers start to get fixed. All this will happen once Mozilla 1.8a6 is released and devs focus on Firefox 1.1 and Thunderbird 1.1 release.

[kainashi]

Missing Search

The search named blocking-aviary1.1+ does not exist.

:huh: thanks for posting anyways though. (Y)

[supernova_00]

Edit: I fixed the query links.

Edited January 9, 2005 by supernova_00

[Alien Venom]

Check out The Burning Edge to find out details about the bugs in nightly builds.

[..Vector..]

Cool, thanks :)

[supernova_00]

Edit: AV, burning edge runs a script that checks the tinderbox for fixes but does not seperate by product. If you want to see what was fixed for Firefox builds each day then check out Peter(6)'s thread in the Build section on Mozillazine Link

Also, if there is a bug you guys want nominated to block 1.1 but do not have a bugzilla account post the bug numbers and I will nominate them. Just remember this release isn't to fix very minor bugs that aren't reproduceable by everyone. Release is mainly to fix some annoying problems that plague everyone. And this release should be a non new features release.

Edited January 9, 2005 by supernova_00

[supernova_00]

Update: Added links to pictures and a video of the new perferences window, cookie contorls and 'sanitize settings'. See bottom of first post for more info and links

[supernova_00]

Just wanted to say that Mozilla 1.8a6 is out so now developement will start to pick up for Firefox 1.1 and the devs will start to go through the above list and either approve or deny for blocking of 1.1. So the graph should really start to look more like a graph in a few days.

[+M2Ys4U Subscriber¹]

line value says 128, but in the bix in the top right, it wasy 125 :) :p

[Pink Floyd Veteran]

wow the setting gui is awsome

and the cookie one is wow too!

[supernova_00]

line value says 128, but in the bix in the top right, it wasy 125 :) :p

585287836[/snapback]

that was because in the Legend it explained that that line was for Blocking + Nominations thats why on the graph it was 128. But I realized there was no point in having that because there was already a line for blocking.

wow the setting gui is awsome

and the cookie one is wow too!

585288808[/snapback]

Ya I hope they both make it for 1.1

[bush]

not so cool new options ui. but we're humans, we can get used to everything ;)

[iwod]

oh my god... how could "we" express our concern for firefox 2?

Close tab on tab button as an option? Why not as an Plug in?

Download manager - Resume should be there at the first place.... But shouldn't other other be offer as Plug in?

Tab broswer. If firefox is allowing Tab browsering than all these optoins of Open which in background.. etc should be there already. Netscape New Broswer Tab option should be looked at .

I always think 30% of the small ( < 10K ) plug in should be as an option in Firefox in the first place, other big things should be as plug in. ( Like Focus last selected tab should have been option in the first place........... not ??)

[supernova_00]

oh my god... how could "we" express our concern for firefox 2?

Close tab on tab button as an option? Why not as an Plug in?

Download manager - Resume should be there at the first place.... But shouldn't other other be offer as Plug in?

Tab broswer. If firefox is allowing Tab browsering than all these optoins of Open which in background.. etc should be there already. Netscape New Broswer Tab option should be looked at .

I always think 30% of the small ( < 10K ) plug in should be as an option in Firefox in the first place, other big things should be as plug in. ( Like Focus last selected tab should have been option in the first place........... not ??)

585293055[/snapback]

Sorry but this thread is only for discussion of Firefox 1.1. 2.0 is more then a year away. btw there are tabbed browsing options in Firefox. type about:config in the address bar, hit enter, filter for 'browser.tab.showSingleWindowModePrefs' and set that to true...if not there then add it. after that go to Tools->Options->Advanced>Tabbed Browsing

[f8tal]

kewl. thx for the preview suprnova.

[supernova_00]

Just wanted to give an update and say that the devs are still working on a plan for 1.1 after that is finalized the bug triage will begin. Hoping for that this week. Also want to say that Asa wants some input on what features the users would like to see for Blogging and form inputs. Comment here

[AaronMT]

When is the estimated release date?

[supernova_00]

Hard to say because the roadmaps are for Developers and the roadmap is for when developers should try and get all the work done. So the target is set for sometime in March so far. So a release will probably be end of March.

[supernova_00]

Update: I made the picture a lot smaller, didn't realize until today at work that the pic was huge even at 1024*768...wouldnt want to see it at 800*600. this also cut down the size by over 100kb.

[PyX]

Sorry but this thread is only for discussion of Firefox 1.1. 2.0 is more then a year away. btw there are tabbed browsing options in Firefox. type about:config in the address bar, hit enter, filter for 'browser.tab.showSingleWindowModePrefs' and set that to true...if not there then add it. after that go to Tools->Options->Advanced>Tabbed Browsing

585295241[/snapback]

Yes, it's more than one year away, 10 KB is nothing right now and will be even more like a joke in one year, if you change your computer in a year, it will be faster and you will have much more space.

I don't see why 10 KB would cause a problem, and since firefox is not bloated, it doesn't hang your system or anything like that.

[supernova_00]

Updates:

From Asa's Blog

We're finally diving headfirst into planning for the Firefox 1.1 release. As many of you know, this release is a minor update without significant feature additions. The goals for this release are primarily to get the Firefox 1.0 code integrated with the latest and greatest Gecko code from the Mozilla development trunk.

If all goes as planned, we'll be syncing all of this up at the 1.8 branchpoint and delivering a Firefox and Thunderbird 1.1 release based on Gecko 1.8. Right now that branch is scheduled to happen in late February or early March with a release from the branch sometime after that.

In order for us to make sure this release is of the highest quality, we're looking for your help in identifying any significant 1.0 problems that need to be fixed for 1.1 and any regressions we've had in the nightly builds since 1.0 shipped.

If you've got cycles to spare, please grab the latest nightly builds of Firefox, use them for your day to day browsing, and report any regressions you find. Also, if you know of bugs that meet either of the two categories above, please nominate them for fixing in the 1.1 cycle by setting the blocking-aviary1.1? flag. The project team will evaluate all of those requests as we start to build the 1.1 buglist.

Just a reminder, this is not a feature release, it's a Gecko update that should provide performance, stability, and website comaptibility improvements for Firefox. We will try to squeeze in a few critical features like Safari migration and default browser settings for Mac that missed the 1.0 boat, but we're not looking for additional feature nominations.

Thanks for your help and I look forward to wading through all of your 1.1 bug nominations :-)

From Ben's Blog

I have been incredibly busy this past two weeks taking care of some important matters, but am now back into 1.1 development. Work on the new Preferences system continues, with only a few things left to do before code review + checkin. A plan for 1.1 is forming in the Mozilla Wiki - any Mozilla/Firefox developers wanting any significant application features should update the plan to include a description and estimate of their intentions!

MozWiki Link

[supernova_00]

Update:

Ben Goodger announced today on his weblog that he has left the Mozilla Foundation to take a position at Google, but will continue his roll as leader of the Firefox project. He gives no details of his or Google's plans, but we expect things like support for Mozilla in Google's desktop search and a Google toolbar for Firefox can't be far off.

Source: Ben's Blog

Please don't discuss this here...Just wanted to post the news. I know this really doesn't deal with 1.1 but it could in a way if google invests time in helping develop firefox like other companies do ie..Sun Microsystems and IBM.

[supernova_00]

^ Follow up on the above post.

Some people have asked if this means that Google has a corporate voice in Mozilla Firefox. The answer is "no." Ben is the Module Owner for Firefox, and as Module Owner he has responsibilities to the Mozilla community. These responsibilities are documented in our policy on Module Owners and Ownership. The key responsibility is that the Module Owner's job is to act in the best interests of the community and the project at large, not in the interests of his or her employer. Ben has lived with these responsibilities as a volunteer, a Netscape employee, a Mozilla Foundation employee and now as a Google employee. We're confident that Ben will continue to help us drive great innovations in the browsing world.

Source: Mozilla Foundation's CEO, Mitchell Baker's Blog

So nothing is going to change with the development be it roadmap, naming, corporate backing or anything else. Firefox 1.1, 1.5 and 2.0 are all still following the same roadmaps.