Platform/2009-05-05: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 17: Line 17:


=== GFX 1.9.1 Update ===
=== GFX 1.9.1 Update ===
* 5 blocking bugs
** 4 of them are image rendering related, either perf or artifacts when zooming
** 1 is the nsWindow destroy bug, which our bandaid attempt didn't fix


=== Layout Update ===
=== Layout Update ===

Revision as of 18:02, 5 May 2009

« previous week | index | next week »

Notices / Schedule

  • Firefox 3.0.11
    • code freeze tomorrow at 11:59pm
    • only a few blockers left though

Blocker Report

Browser / Front End

  • Polish update: Firefox is 55% shiny (+2% over two weeks ago)

pub?key=pMZGKUlD9NOPg4oJGs1CUMw&oid=1&output=image&foo=.png

GFX 1.9.1 Update

  • 5 blocking bugs
    • 4 of them are image rendering related, either perf or artifacts when zooming
    • 1 is the nsWindow destroy bug, which our bandaid attempt didn't fix

Layout Update

  • Roc is not available today
  • Layout
    • 5 blockers on trunk (3 with patches)
    • 10 untriaged noms (3 fixed)
  • SVG
    • 0 blockers
  • Video/Audio
    • 19 blockers (6 with patches) (could be pruned, should not delay our schedule)

Content Update

Mac OS X Update

JS 1.9.1

General 1.9.1

Mobile 1.9.1 Update

Security

Multi-Process

  • Initial docs with phases and SWAG schedule available.
  • Initial focus will be responsiveness/stability, not security sandboxing
  • We're looking for places where chrome JS currently touches content DOM directly... see mozilla.dev.platform post for more details.
  • Decisions need to be made about how to approach the network stack (should we switch to chromium's network stack wholesale?), but I don't know the right way to have that conversation/make that decision (it's hard to know whether switching would reduce or extend the total time of the multiple-process work).

Tree Management

Roundtable

  • If worked on a user facing feature, please make sure it is on this list (which will be used to generate the press reviewer's guide, mozilla.com content, etc):