Platform/2009-Q3-Goals: Difference between revisions

Line 72: Line 72:


=== Content ===
=== Content ===
* HTML5 parser
* Continue implementation of HTML5 parser.
** Advertise the HTML5 parsers availability to testers to get more feedback.
** Advertise the HTML5 parsers availability to testers to get more feedback.
** Off main thread HTML5 parsing as a prerequisite for turning HTML5 parsing on by default.
** Off main thread HTML5 parsing as a prerequisite for turning HTML5 parsing on by default.
** Propose a long term plan for the generated C++ in the HTML5 parser.
** Propose a long term plan for the generated C++ in the HTML5 parser.
* XBL2
* Make significant progress on XBL2.
** Attachment, detachment, through all three binding mechanisms.
** Attachment, detachment, through all three binding mechanisms.
** Initial rendering of the shadow tree.
** Initial rendering of the shadow tree.
** Insertion points (<children>).
** Insertion points (<children>).
* Extension security and ease of development
* Improve extension security and ease of development
** Design and implement an way for JetPack to safely expose APIs to untrusted code.
** Design and implement an way for JetPack to safely expose APIs to untrusted code.
** Propose an API to add names to the global namespace from JS extensions.
** Propose an API to add names to the global namespace from JS extensions.
* Improve DOM performance
* Improve DOM performance.
** Evaluate the feasibility of proposals such as IndexOf() redesign (per bz's proposal in mozilla.dev.tech.dom) and changing DOM node child list storage from array to linked list or maybe B-tree with backpointers from DOM-nodes to B-tree nodes.
** Evaluate the feasibility of proposals such as IndexOf() redesign (per bz's proposal in mozilla.dev.tech.dom) and changing DOM node child list storage from array to linked list or maybe B-tree with backpointers from DOM-nodes to B-tree nodes.
** Profile DOM performance problems beyond the JS to C++ bridge.
** Profile DOM performance problems beyond the JS to C++ bridge.
* Multi-process networking
* Implement a prototype of multi-process networking.
** Write a test application with a child process that does plain HTTP over IPC through necko in the main process.
** Write a test application with a child process that does plain HTTP over IPC through necko in the main process.


Confirmed users
1,067

edits