« previous week | index | next week »

Notices / Schedule

Gecko 1.9.3a1

• plan to freeze mozilla-central Thursday evening, build Friday, release early next week
  • does this work?
  • how long do we hold / what risk do we take to ship with OOPP on?
• still need to figure out branding
• 1.9.3 Triage: 149 nominations
• 1.9.3 alpha 1: 5 Open blockers
• features we want alpha testing on: please add anything missing to the list
• have a look at the list of top crashes in Monday's Windows mozilla-central nightly, top crashes in Tuesday's Windows mozilla-central nightly (should be useful late Tuesday / early Wednesday)

Blocker Report

Browser / Front End

Behold, a mere sampling of the mighty awesome that the Firefox team hath wrought:

Lorentz

• UI for crashed, out-of-process plugins basically done bug 538910

Firefox.Next

• Getting close to having the ability to specify custom actions for each update. See Rob Strong's blog post, bug 530872 and bug 538331
• Stephen Horlander exploring changes we want to make to tab animation (creation, re-ordering, tear off).
• Check Boriss' blog for discussion about the new look and function of the extension manager
• Marco added a ton of awesome to browser chrome test harness, including common headers, clean up functions, and timeout extensions. Already cleared a few intermittents.
• Progress on various UI perf and responsiveness bugs (bug 520659, bug 536893, bug 528884)

See the active projects page for the complete list of active work by the Firefox team.

GFX Update

• Several projects are still ongoing:
  • Cairo update & merge
  • Direct2D/DirectWrite patch reviews and updates
  • Windows out-of-process plugins work - there's one large outstanding issue that Jim is working on.
  • Core Animation plugin support attempts - three independent attempts to support them, each with their own issues. Benoit is still working.
  • Fennelectrolysis shared memory work hopes to wrap up this week.

For more, see our weekly meeting page.

Layout Update

• Found Windows "exit code 1" orange. Need to keep working on orange bugs. How do we get people working on them?
• Fullscreen API proposed in WHATWG mailing list; please investigate. email thread starts here and here

Content Update

• Landed HTML5 pushState (Justin Lebar, Jonas)
• Worked on branch back porting (mrbkap, jst)
• Atom table patches ready and up for review (Jonas)
• Attended the Velocity summit. Feedback collected at Performance:Velocity2010 (Jonas)
• Investigating what we need from electrolysis to do our security notifications right, for the lock icon etc (Honza)
• Got large parts of content process event handling done, tests included (smaug)
• HTML5 parser related about:blank work, and mochitest investigation (hsivonen)
• CPOWs are getting easier and easier to use (bnewman)

Platform-specific Support Update

JS

• nanojit work winding down for the moment
• new baseline compiler starting up

Electrolysis

• Plugins
  • Windows hangs edge cases still bedeviling: jimm on it (today?)
  • Two most obvious crashes dealt with today (bug 542248, bug 543376
  • One more topcrash diagnosed, perhaps dealt with today bug 542263
  • UI needs to land
  • status for 1.9.3a still ambiguous: either off-by-default or manipulate prefs so that only flash and silverlight are on by default

• Fennec
  • Benedict starting on webprogresslistener
  • smaug has event listeners almost ready, might need CPOW
  • benjamn has CPOWs, need review... can somebody other than bsmedberg review this?
  • romaxa working on Qt
  • joe, memory-mapped drawing?

• Jetpack
  • jdm working on multi-process jetpack with CPOW support

Startup Performance

Summary

• Read the latest weekly update.
• View snapshot results for startup and all other tests.

Priorities

More

• Rob Campbell did research on Mac build optimizations.
• More details on the project page.
• Join us on IRC in #startup.

Security

Breakpad

• DWARF CFI support submitted to Google for review. 6 of 12 patches approved; waiting for review on others.
• .eh_frame support bug 543542
  • .eh_frame is a minor variant of DWARF CFI that the Linux C++ implementation uses to walk the stack to find exception handlers. Since it effectively provides the same stack-walking information as DWARF CFI, the toolchain omits DWARF CFI if the object file has .eh_frame data. Expecting to submit patches to Google for review today or tomorrow.
• DWARF debugging information: contributors showing up to extend functionality.

Tree Management

• switching from rev2 to rev3 talos hardware
  • when is the best time?

Roundtable

Firebug

• bug 542203 - fixed in Yslow, diff on-hand
• bug 542120 - crash freq. increasing
• bug 541390 - still unverified, but likely a freeze from the past

other highlights

• getfirebug.com refresh released
• 1.5.1 scheduled for next week