Platform/2010-Q1-Goals: Difference between revisions

Line 40: Line 40:


=== [[Platform/2010-Q1-Goals/Content|Content]] ===
=== [[Platform/2010-Q1-Goals/Content|Content]] ===
* {{risk|Move the web forward by landing WebSockets, enabling the HTML 5 parser by default, and/or finishing more File spec API improvements (i.e., File.url).}}
* {{miss|Move the web forward by landing WebSockets, enabling the HTML 5 parser by default, and/or finishing more File spec API improvements (i.e., File.url).}}
** {{risk|WebSockets has r+, but needs another review. Reviews may happen, but testing infrastructure for it is unlikely to be ready}}
** {{miss|WebSockets has r+, but needs another review. Reviews may happen, but testing infrastructure for it is unlikely to be ready}}
** {{risk|HTML 5 parser code is likely to be done, and reviewed, but testing infrastructure is lagging behind and is unlikely to be ready by the end of the quarter.}}
** {{miss|HTML 5 parser code is likely to be done, and reviewed, but testing infrastructure is lagging behind and is unlikely to be ready by the end of the quarter.}}
** {{done|File API stuff is done.}}
** {{done|File API stuff is done.}}
* {{ok|Ship out of process plugins betas for windows and continue forward progress on full Electrolysis plans by getting basic HTTP working across processes and implementing multi-proc event handling.}}
* {{ok|Ship out of process plugins betas for windows and continue forward progress on full Electrolysis plans by getting basic HTTP working across processes and implementing multi-proc event handling.}}
** {{ok|OOPP}}
** {{done|OOPP}}
** {{ok|HTTP across processes}}
** {{ok|HTTP across processes}}
** {{done|e10s event handling}}
** {{done|e10s event handling}}
* {{ok|Improve performance by eliminating more cycles between JIT generated code and our DOM code, and by speeding up our DOM implementation as well.}}
* {{ok|Improve performance by eliminating more cycles between JIT generated code and our DOM code, and by speeding up our DOM implementation as well.}}
* {{risk|Investigate (and fix as needed) the impact of Firebug on Firefox performance and memory usage}}
* {{miss|Investigate (and fix as needed) the impact of Firebug on Firefox performance and memory usage}}
** Implement back-end functionality for allowing Firebug to hook into document load and unload to eliminate perceived performance problems with the use of Firebug.
** Implement back-end functionality for allowing Firebug to hook into document load and unload to eliminate perceived performance problems with the use of Firebug.


Confirmed users
839

edits