Summit2008/Sessions/Proposals/Content Team Planning

From MozillaWiki
Jump to: navigation, search
Title
Content Team Planning
Leader
Johnny Stenback

Summary

The members of the content team are rarely all in the same place at the same time so we'd like to take this time to talk face to face about future work that's on the table for the content team.

Agenda

The exact agenda of the meeting is TBD, but some of the features we should discuss are:

  • HTML parsing on a different thread.
    • Where to draw the line between the parser thread and the main thread.
    • Who will work on this...
  • Optimistic HTML script loading
  • DOM worker threads, near and far.
    • XHR-X on worker threads, how to do it.
  • Clean up passing of arrays through IDL
  • Mainthread && CC docshell
  • Kill CAPS policy prefs
  • Web API for session history
  • DOM Perf Tests (Dromaeo)
  • HTML5 parser
  • Database API?
  • Web Sockets?
Title
Content Team Planning
Leader
Johnny Stenback

Summary

The members of the content team are rarely all in the same place at the same time so we'd like to take this time to talk face to face about future work that's on the table for the content team.

Agenda

The exact agenda of the meeting is TBD, but some of the features we should discuss are:

  • HTML parsing on a different thread.
    • Where to draw the line between the parser thread and the main thread.
    • Who will work on this...
  • Optimistic HTML script loading
  • DOM worker threads, near and far.
    • XHR-X on worker threads, how to do it.
  • Clean up passing of arrays through IDL
  • Mainthread && CC docshell
  • Kill CAPS policy prefs
  • Web API for session history
  • DOM Perf Tests (Dromaeo)
  • HTML5 parser
  • Database API?
  • Web Sockets?

Discussion outcome

  • HTML parsing on a different thread.
    • Need to figure out how this plays into the HTML5 parsing initiative. Should set up a discussion between hsivonen (who's working on the HTML5 parser), mrbkap, benjamn, jonas, jst, boris, peterv to figure out what makes the most sense scheduling wise.
  • Optimistic HTML script loading
    • mrbkap's got this limping along, hoping to get it in for 1.9.1, but BlackHat and DefCon conference attendance makes it tight scheduling wise.
  • DOM worker threads, near and far.
    • Need XHR (minus XML parsing). Must be done on the main thread anyways because AsyncOpen etc in necko is *not* thread safe, so proxying over to the existing XHR with some tweaks to it is probably the way to go here.
  • Clean up passing of arrays through IDL
    • Should work on this, but not 1.9.1 material. Convenience is probably the biggest factor here, i.e. being able to pass nsTArray<> or some variation through IDL stuff.
  • Mainthread && CC docshell
    • Patches mostly done for both of these, probably doable for 1.9.1.
  • Kill CAPS policy prefs
    • Thunderbird/mailnews is the big user of this, need to figure that out by discussing this with the relevant people. Firefox also depends on policy prefs for allAccess properties, but there's only a handful of them, could fairly easily hardcoded or what not.
  • Web API for session history
    • Jonas will look into this, should be pretty straight forward, trivial API. Potential for 1.9.1
  • DOM Perf Tests (Dromaeo)
    • jresig wrote these awesome tests, and will work on getting them into the automated testing infrastructure, partially or completely.
  • HTML5 parser
    • See above.
  • Database API?
    • Lots of open questions, not 1.9.1 material. API still unclear, lots of usecases but no clear driver.
  • Web Sockets?
    • Also lots of open issues, not 1.9.1 material.
Retrieved from "https://wiki.mozilla.org/index.php?title=Summit2008/Sessions/Proposals/Content_Team_Planning&oldid=102588"