Ian Hickson Weekly QA Status

Week Ending 2000-10-27

Project Testing - Planning and Coverage Tasks Conducted

5.0

• General
  • Reviewed, proof read, submitted comments regarding and discussed in detail with engineers the XBL specification (work towards a CSS module) in preparation for Netscape's proposal to the World Wide Web consortium and Microsoft.
  • Minimised CSS crashers (potential mail or IM exploits - urgent RTM work).
  • Attempted to produce exploit for CSS/DOM privacy bug (urgent RTM work).
• Testing Documentation Development, Reviews and Updates
  • Worked on DOM2 Style test suite matrix.
  • Wrote release notes for important bugs.
  • Discussed some problems with bugzilla keywords with mozilla.org.
• Testcase Development, Reviews and Updates
  • Created 10 attachments in Bugzilla (testcase) after narrowing bugs.
  • Created 2 serious crasher test case.
  • Worked on tests for the DOM2 CSS test suite.
• Testing Conducted
  • Performed testing of DOM2 CSS in parallel with test case creation, including filing new bugs.
  • Performed brief functional testing for press CD candidates
• Bug Management
  • NEW: 8.
  • REOPENED: 5.
  • VERIFIED: 3, vtrunk: 1.
  • INVALID: 3.
  • WORKSFORME: 3.
  • WONTFIX recommendations: 2.
  • DUPLICATE: 5.
  • RELEASE NOTE ITEMS: 4.
  • DETAILED COMMENTS: 15.
  • TRIAGED: 8.
  • Made a total of 124 bug modifications.
• Hot Bugs
  • There are many CSS bugs that are going to cause serious problems to web authors (when they find their web pages don't work in N6), web users (when they find web pages don't look right in N6) and us (when we release N6.5 and thus break all the pages dependent on our current broken behaviour) if they are not resolved before RTM. Whine, whine. Unfortunately PDT have prioritised these bugs out of the stratosphere. Some of these bugs are mentioned below. I stopped short of giving a full list of the serious CSS1 compliance bugs since that would take ages. This is the same list as last week, nothing has changed.
  • bug 3935: mozilla-native psuedo classes and properties should be marked as such
  • bug 4831: float should not be higher than earlier float on opposite side
  • bug 12272: clear not clearing previous floating siblings of ancestors
  • bug 41412: text overlapping top edge of pushed-down float
  • bug 46291: float should not be higher than cleared float on same side
  • bug 53974: hovering over paragraph with generated content repeats content
  • bug 3490: line-breaking bug caused by -ve margin-right on inline elements
  • bug 46918: line-breaking bug caused by +ve margin-right on inline elements
  • bug 5693: problems with :hover (the full fix, not the performance fix)
  • bug 2942: non-CSS presentational hints and user stylesheets
  • bug 43220: author !important rules override user !important rules in user.css
• Project Related Issues/Concerns/Successes
  • Many serious CSS1 bugs remain, see "Hot Bugs" section.
• Plans for Next Week
  • Continue to comment on all relevant bugs.
  • DOM2 CSS test development
  • RTM testing

SusEng QA Support

• General Issues Concerns
  • none
• Testing Conducted
  • none
• Hot Bugs
  • none

Server/Lab HW-SW Updates

• none

The Personals!

• Jay completely killed me at Monopoly. Next week, I shall win.