MozillaWiki

Platform/2008-Q2-Goals: Difference between revisions

< Platform
 
(6 intermediate revisions by 2 users not shown)
Line 8: Line 8:


* Finish Gecko 1.9 work for release.
* Finish Gecko 1.9 work for release.
* Create and begin following through on plans for Firefox 3.1 based on Firefox 3 feedback.
* Create plans for Firefox 3.1. By the end of Q2 we should have decided exactly what features and fixes the Mac OS X group will contribute to Firefox 3.1. Decisions should be written up with specific details in the Mac OS X section of wiki.mozilla.org.
** Most likely going to mean implementing Mac OS X look-and-feel features that we simply weren't able to finish for Firefox 3.0.
* Create plans for Mozilla 2 work. By the end of Q2 we should know what the first priorities will be for each Mac OS X group member once we start work on Mozilla 2 nearly full-time. These priorities should be written up with specific details in the Mac OS X section of wiki.mozilla.org.
*** Identify and fix 1 major look and feel issue for Firefox 3.1
* Start thinking about Mac OS X requirements for a widget testing framework. What widget functionality can we realistically test with automated tests and how might we execute such tests? Of the functionality we can test, what needs testing most? Progress answering these questions should be written up on wiki.mozilla.org in a new section covering widget testing plans.
* Start work on Mozilla 2.
** P1, Decomtaminate nsIMenu and nsIMenuItem, clean up nsIMenuBar interface.
*** Estimated to take Josh 1 week.
** P2, Clean up widget cross-platform XPCOM interfaces (widget/public/*)
*** Have Josh spend 1 week doing this in the first half of June.
** P1, General work to reduce Cocoa widgets code complexity and improve clarity.
*** Have Josh spend 2 weeks doing this in the second half of June.
** P2, Make some progress towards 64-bit Gecko on Mac OS X. Examples include...
*** remove Carbon API usage
*** create plan for native types in Mac OS X code
*** create build configuration for 64-bit
* Create plan for widget testing framework. This is going to be a difficult long-term project but we should be able to get through a good amount of the planning in this quarter. This will require more time to develop than most testing frameworks we have in place did because it is low-level, scriptability for native event handlers is difficult (we'll essentially have to figure out how to simulate native events on each platform), and the widgets "spec" is weakly defined.


=== Content ===
=== Content ===
* Add support for Content Restrictions of some kind
* Implement a background content sink that continues searching for resources to load during script execution
* DOMParser for text/html


=== JS ===
=== JS ===
* Performance
** iteration, numeric, string manipulation and closures
** build work (source refactoring, compiler tweaks)
** code generation for assignments and other common patterns
** DOM: expando optimizations
* ES4 early implementation
** library additions cherry-picked from stable spec parts (bind, expand, catchalls), etc.
** as few new-syntax cases case possible
* DOM: mozilla.JSON
* DOM: worker threads


=== Toolkit ===
=== Toolkit ===
Line 35: Line 38:


=== Additional Goals ===
=== Additional Goals ===
* Add support for dwarf2 Mac symbols to Breakpad

Latest revision as of 15:42, 18 April 2008

Goals Summary

Layout

GFX

Mac OS X

  • Finish Gecko 1.9 work for release.
  • Create plans for Firefox 3.1. By the end of Q2 we should have decided exactly what features and fixes the Mac OS X group will contribute to Firefox 3.1. Decisions should be written up with specific details in the Mac OS X section of wiki.mozilla.org.
  • Create plans for Mozilla 2 work. By the end of Q2 we should know what the first priorities will be for each Mac OS X group member once we start work on Mozilla 2 nearly full-time. These priorities should be written up with specific details in the Mac OS X section of wiki.mozilla.org.
  • Start thinking about Mac OS X requirements for a widget testing framework. What widget functionality can we realistically test with automated tests and how might we execute such tests? Of the functionality we can test, what needs testing most? Progress answering these questions should be written up on wiki.mozilla.org in a new section covering widget testing plans.

Content

  • Add support for Content Restrictions of some kind
  • Implement a background content sink that continues searching for resources to load during script execution
  • DOMParser for text/html

JS

  • Performance
    • iteration, numeric, string manipulation and closures
    • build work (source refactoring, compiler tweaks)
    • code generation for assignments and other common patterns
    • DOM: expando optimizations
  • ES4 early implementation
    • library additions cherry-picked from stable spec parts (bind, expand, catchalls), etc.
    • as few new-syntax cases case possible
  • DOM: mozilla.JSON
  • DOM: worker threads

Toolkit

Build System

Mozilla 2

Additional Goals

  • Add support for dwarf2 Mac symbols to Breakpad
Retrieved from "https://wiki.mozilla.org/index.php?title=Platform/2008-Q2-Goals&oldid=90666"