shaver

what is "aggressive use of connection pre-caching"?
- added notes to help explain -- beltzner
what is "cache entropy on crash"?
- added notes to help explain -- beltzner
we already have two types of offline data storage for web developers (localStorage and the resource cache) -- what else is specifically required for Namoroka?
- removed -- beltzner
what sorts of user interface animations need to be supported? affine transformations? all CSS properties? custom blending or processing?
- this will be determined in the exploration phase -- beltzner
has the "no new features after beta1" plan been proposed to platform developers?
- not outside of this document -- beltzner

Artir

The user interface must be part of alpha test/feedback, beta is really too late.
- Agreed. Under this plan there will be many alpha milestones which will contain user interface iterations based on the various prototypes, but that will solidify by the time we reach beta. During beta, small changes to the user interface will be permitted, but only due to wider feedback. Beltzner 14:53, 1 April 2009 (UTC)

Test-case development should be started in conjunction with the writing of the functional specifications.
- Yup, that's part of the Template. Beltzner 14:53, 1 April 2009 (UTC)

Both windows 7 and snow leopard will have location services. Our geolocation implementation should make use of these system services.

Perhaps a couple of small tweaks:

For the Performance goal, Mozmill scripts may be a good ways getting performance numbers per actual use by an end user. Examples include:
- Opening 1,000 tabs and visiting sites in each. (while not common, there _are_ folks who use an insane number of tabs - and there have been reports of lagginess or similar when there is such a large number of tabs)
- Going to random sites in hundreds of tabs, along with opening bookmark windows etc., while not restarting Firefox for a certain number of days.
- Or something similar.
- Reference at mozmill-dev thread.