Platform/2010-06-15: Difference between revisions

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


= Content Update =
= Content Update =
* Necko e10s changes getting close to landing in mozilla-central (jduell)


= Platform-specific Support Update =
= Platform-specific Support Update =

Revision as of 18:00, 15 June 2010

« previous week | index | next week »

Notices / Schedule

  • Firefox 3.6.4
    • The release -> beta channel update was successful
      • Release channel went from 325k -> 124k in 3 days, build #6 users specifically 211k -> 30k
    • Built build #7 for bug 562198 on Friday
    • Released build #7 to beta users yesterday afternoon
    • Plan is to release build #7 as Firefox 3.6.4 final on Thursday, 2010-06-17
      • Is this date ok? Concerns? Outstanding bugs I should be aware of? Resource conflicts?
      • Will have small uptake, but build #6 baked for a long time and the changes on top are fairly small
  • Firefox 3.5.10
    • Tied to 3.6.4
  • Firefox 3.6.6
    • Announced the 1.9.2.5 -> 1.9.2.6 change on planet and planning
    • Will be coming up with some scenarios and schedules this week for review
  • Mozilla Developer Preview 5 (aka 1.9.3a5)

Blocker Report

  • Firefox 3.6.4
    • Nothing blocking, but watching this query to make sure nothing is missed

Browser / Front End

GFX Update

  • Harfbuzz landed! bug 449292
    • It's turned off by default. To turn it on:
      • Set gfx.font_rendering.harfbuzz.level to 1; harfbuzz will be used for "simple" scripts (Latin, Cyrillic, CJK) that do not require specific complex shaping.
      • You can set it to 2; Harfbuzz will then be used for all scripts (even though the results will currently be broken).

Hardware Acceleration Update

  • OpenGL and OpenGL ES acceleration won't make it for Q2.
    • To talk more about this, please participate in the dev.planning thread.

Layout Update

  • WebM landed and shipped in 1.9.3 alpha.
    • Need to work on performance, especially non-accelerated scaling; will probably use more of the Chrome code [doublec]
    • Working on 'buffered' TimeRanges; implemented for Ogg and Wave, working on WebM [cpearce, kinetik]
  • Harfbuzz landed, currently off by default [jkew, jdaggett]
  • Retained layers basically ready for review, just wrangling a few test failures [roc]
    • Optimized scrolling of background-attachment:fixed in hard cases (faster than Safari)
  • Reorganization of frame coordinate systems for zooming just about ready for review [tnikkel]

Content Update

  • Necko e10s changes getting close to landing in mozilla-central (jduell)

Platform-specific Support Update

JS

Electrolysis

Startup Performance

Security

Breakpad

Tree Management

  • New mozilla-1.9.3 / mozilla-2.0.0 branch work blocked on figuring out which version # to use

Roundtable

  • Are we happy not including the XPCOM changes (and any related Gecko version bump) in beta 1? (Mossop)
  • Some feedback from Linuxtag (Pike):
    • Getting rid of restarts, updates not in startup is a perfect match with people
    • Hard to tell how much of perf comparison with chrome is apples-to-apples, both in platform integration and extension ecosystem/capabilities. Recent blog and forum posts helped.
    • Having plans for shoveling tasks to other processes and GPU is good, should deliver something noticeable in Fx4
    • Adblock+ is something like a Firebug, in that people evaluate "the browser that run adblock+". Recent perf blog by Wladimir helped a bunch, but people don't mind that much who's at fault. Can we expose better APIs for him?