Platform/2009-05-05: Difference between revisions
< Platform
Jump to navigation
Jump to search
(multi-process) |
|||
| Line 6: | Line 6: | ||
=== Browser / Front End === | === Browser / Front End === | ||
* Polish update: Firefox is 55% shiny (+2% over two weeks ago) | |||
** Thanks go to: marco, dao | |||
** 44 remaining [http://tinyurl.com/8qnba2 easy polish bugs] (whiteboard [polish-easy]) | |||
** 38 remaining [http://tinyurl.com/9zq9xz hard polish bugs](whiteboard [polish-hard]) | |||
http://spreadsheets.google.com/pub?key=pMZGKUlD9NOPg4oJGs1CUMw&oid=1&output=image&foo=.png | |||
=== GFX 1.9.1 Update === | === GFX 1.9.1 Update === | ||
Revision as of 17:42, 5 May 2009
« previous week | index | next week »
Notices / Schedule
Blocker Report
Browser / Front End
- Polish update: Firefox is 55% shiny (+2% over two weeks ago)
- Thanks go to: marco, dao
- 44 remaining easy polish bugs (whiteboard [polish-easy])
- 38 remaining hard polish bugs(whiteboard [polish-hard])
GFX 1.9.1 Update
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).