maintained by Tim Rowley <firstname.lastname@example.org>
Last Updated Thursday April 4, 2002
This status update page is updated every
week. To get updates and news throughout the
week you are invited to check out mozillaZine
a site devoted to Mozilla advocacy.
- Great many fixes coming through.
- Triaging continues!
- fixed bug 116365 "[RFE] Cache partial documents; automatically issue byte range requests"
- fixed bug 132329 "HTTP auto goes into infinite loop"
- fixed bug 130301 "Cannot submit large POST requests since Mozilla 0.9.9"
- developed initial patch for bug 129279 "nsIFile unicode/utf8/ascii task"
- reviewed patches
- triages bugs
- Continued work on bug 81724 "disk cache needs stream wrappers" needed to support partial cache entries.
- Working on using a flatfile to cache plugin info, instead of using libreg registry, bug 109939 - plugins registered in appreg each time they are used.
- Triaged bugs.
- checked in fix for stripes appearing in images while scrolling. bug 83289
- Working on timer DHTML regression
- Fixed a bug with status/reports tool-- removed the username from under summary section in group consolidated reports.
- Significant progress made on mozpoint-- getting it ready for it's first run tomorrow!
- Out sick for part of week with fever and flu.
Plans for next week
- continue developing nsIFile patch
- begin patch for http pipelining
- triage bugs
- Fix the timer DHTML regressions. bugs 117061, 120417
- I believe I have a fix for topcrash bug 119693. Will continue testing to verify it does not regress anything.
Heads up on priority items
- nsbeta1 progres
- nsbeta1+: 32 (-7); nsbeta1: 20 (+/-0).
- topembed progress (excluding nsbeta1)
- topembed+: 2 (+/-0), topembed: 0 (-3).
- P3P progress
- Human readable policy viewer looks good. Working on machine
readable (XSLT generated); mostly done. UI almost done. Will provide test
builds this week. Will test on top 800 sites or so.
- P3P will be checked into the Netscape tree since mozilla.org
has some issues with it.
- Worked on p3p policy viewer (bug 124503). Spent major portion of the time creating stylesheet ( xsl ). Got together
with Samir to work on P3P FE.
- Worked on JS line number issue (bug 111576).
- Did code reviews.
- Fixed bug
131311. Made window.scrollX and .scrollY "replaceable" for backwards
- Fixed bug 132904. Made window.clearTimeout() and .clearInterval() callable with no arguments
or with an undefined argument for backwards compatibility.
- Finally fixed all known problems with my iframe loading
bug (bug 52334), now waiting for approval to check it in.
- W3C DOM work.
- Reviewers' guide work
- Looking at old fixed exploits, re-testing and writing
- Code reviews for peterv, harishd, jst
- Wrote a small Perl script that reads a sitelist and
tries to see which sites carry a P3P policy. This will help us test P3P.
The script is attached to bug 124503.
- Fixed bug 86583,
made it possible to drag and drop images, image map links and XLinks.
- Fixed bug 93218,
added cookie support for XML.
- Made fix for bug 126669, saving XHTML makes documents non-wellformed.
- Became super-reviewer, my preferred areas are XML,
content, htmlparser, expat. Go easy on the requests, I am also a manager
Plans for next week
- Continue fixing mozilla1.0 bugs.
- Land my iframe loading changes.
- Fix one more 1.0 security bug
- Keep working on reviewers' guide
- Fill survey.
- Make fixes for remaining bad XML regressions.
- Make sure our intern offers get on their way.
Recently someone attacked most of the mozilla.org mailing
lists as well as several individuals by subscribing them to
more than a hundred mailing lists. While its possible to
unsubscribe from these lists, the volume of subscription
notifications alone is overwhelming.
If you are a victim of this attack read
this article to find out how to
help the AOL
operations security team investigate this incident.
This last week drivers approved about 150 fixes. Drivers will be much
more conservative in approvals as we work to get a branched and to make
a Mozilla 1.0 Release Candidate happen. The current thinking is to
branch on Monday, April 8 and get RC1 out the door sometime that week.
Bugs we need fixed in order to get branched and make RC1 are being
tracked in the dependency tree at bug 134771. This tracks the minimal set of fixes that
we need in order to have a useful Release Candidate so if you own one of
these bugs or can help one of the owners with other bugs, reviews or
super-reviews then please make this a top priority.