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.

blizzard

• I've heard a lot of good feedback on the chrome download manager - can we spend some time during the prototyping period to look and see if we can make some improvements?

Adam757

• IEAK style administration kit, allowing flexible, locked-down settings deployment for corp. environments

johnath

• about:support - We should not let this slip another release - it's a great force-multiplier - a small amount of developer time to make our support organization loads more effective. https://bugzilla.mozilla.org/show_bug.cgi?id=367596

skierpage

pay little attention, just a user :-)

Re [P2] support file management tasks (delete, move, etc) in download manager

I think the Download manager should be another view in Places (the Library window). Places should remember info about URLs you've saved, and then turn around and let you view and manage the local file://path URLs to which you've saved/downloaded. Tagging, starring, viewing information about downloads such as when saved, the URL you downloaded and the URL of the page where you downloaded; all have a natural fit with Places data.

How are you going to support file move/copy management? You could give Places yet another view, a file system view similar to Windows Explorer. Already its navigation pane looks almost identical to Explorer Bar > Folders view in Windows. It might be natural to organize local file:// URLs by showing the directory structure into which you downloaded them.

Talk is cheap, but I'll try to flesh out these ideas at User:Skierpage/Places as a next-gen file manager

-- Skierpage 01:27, 13 May 2009 (UTC)

Mute Background Music

Sometimes we visit websites with a background music which we can not control unless we lower or mute the sound from the master control. I think it will be useful if we can mute that sound without affecting the sound coming from the other tabs and windows of FireFox.

Electrolysis

It seems that Electrolysis is planned within the same timeframe as 3.6's development process. If all goes well, will it be seen in Namoroka? --RayneVanDunem 17:46, 29 May 2009 (UTC)