Reporting and Nominating Bugs for Mozilla Firefox 1.0

Thursday April 29th, 2004

Ben Goodger writes: "We're beginning the drive to Firefox 1.0 and we need to make sure that every bug people think is important is filed in Bugzilla and has a blocking0.9? or blocking1.0? request flag set. This will allow the FDT (heh) to develop an action plan for the milestones between now and 1.0, prioritize bugs and so on. It's essential that people start doing this now, rather than later, otherwise bugs might slip through the cracks!" Further details are available in Ben's posting to the Firefox forums.

#62 Re: Re: Re: Re: Re: Re: Re: We are all wasting tim

by bzbarsky

Friday April 30th, 2004 11:31 PM

You are replying to this message

As I recall both TBE and whatever the other popular tabbrowser extension was had security holes (some of which were even shared by Firefox itself, but they got patched in firefox and I'm not sure anyone contacted the extension authors).

I don't recall the details, because frankly I don't have time to follow all the extensions or indeed Firefox itself. I just recall the problem being discussed on irc at some point.

> I see a lot of talk about "No one reviewing code", trusting extensions etc, and yet no help at all resolving > these issues.

How do you suggest these issues be resolved? I actually read through the TBE code once. It was reproducing about every single view-source-and-cache-interaction bug that had ever been fixed in the SeaMonkey UI... What should my reaction be, given that I don't use the extension (or the browser it's an extension for) and don't really care about it? I think I dropped the author some mail urging him to read the CVS logs for the relevant SeaMonkey code, but....