Talk:Firefox/Namoroka/Initial Plan

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

• And what about Linux integration?
• GNOME key-manager, Notify-OSD for notifications, for example.

MacMel

• 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)

DougT

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

jwatt

Perhaps a couple of small tweaks:

• s/intended release target/tentative release target/
• s/properly investing time/best investing our time/

nth10sd

• 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.

Nathaniel

I love the Task Based Navigation idea, and especially the tab grouping aspect. Along those lines, I think my concept Tab Grouping might be an interesting starting point for conceptualizing what this will entail. I look forward to your feedback.

Security

A few security-related suggestions:

• Windows

 * Support Vista and Windows 7 64-bit systems
 * 64-bit executable runnable with HW DEP and ASLR
 * Optimized for Core 2 Duo and later Xeons with 64-bits, NX, SSE2, SSE3, SSSE3

• MacOS X

 * Support Leopard and Snowleopard 64-bit systems
 * 64-bit executable supporting all snowleopard security features (still hazy?)
 * Optimized for Core 2 Duo and later Xeons with 64-bits, NX, SSE2, SSE3, SSSE3

• Linux

 * Support 64-bit versions
 * 64-bit executable
 * Support whatever security is generally available
 * Optimized for Core 2 Duo and later Xeons with 64-bits, NX, SSE2, SSE3, SSSE3

• Although some code may slow down ~10% with longer addresses, use of the XMM registers greatly speeds up some code as well. Overall, I would expect performance to be about the same based on other benchmarks. Not everyone will be able to run these binaries, but, IE8 on Vista 64 already has these enhancements, and I would hate to see Firefox not have them available.