Actions

Gecko Meeting

"Print layout should look like rendered layout"
- Needs to be clarified and better defined
- Actual use cases and possible test cases are needed to figure out how this is broken
"Layout should be zoomed/cropped to fit desired page size"
- Bug numbers needed or bugs need to be filed
"Printed material should match user expectations"
- Needs to be more clearly defined
"Save web pages as PDF"
- Vlad and Pav to investigate further
"Provide infrastructure for an extensible Web page archiving system"
- Someone needs to investigate how other browsers (ie5 on mac, omniweb, etc) approach this problem
- Do we care enough about this to assign as part of Fx3 or will it be followed up on through a Labs project? Someone needs to figure that out.
"TTS/Screenreader support"
- Someone needs to follow up on this by asking Aaron Leventhal if we already have it, and, if not, what it would mean to implement it.
"CSS 2.1"
- Specifics need to be sorted out. To be discussed by brendan, dbaron, roc. We need a set of specific and trackable line items (with priorities) for this.
"CSS 3 features"
- As with CSS 2.1, specifics need to be sorted out and turned into trackable line items for the PRD.
Offline apps
- Further investigation and refinement required. Meeting needs to be scheduled.

"Remove extension installation whitelist"
- Requires investigation to sort out how better this problem can be solved for users. Whoever does the design should work with dveditz.
Extension first-run experience
- Some extension first-runs pop up windows and dialogs, which is very jarring. Someone needs to think about how better to do that sort of thing. Extension authors should use the same model as Fx (notification system, UI flow). "Best practices" and evangelism required here as well -- shaver + DevRel team.
We are expecting some possible line items from shaver re: Add-ons section of the PRD, so someone needs to follow up on that after the Remora launch.
Rob strong needs a solid UI design provided for the addition of Add-ons configurations into the prefs panel. UI/UE team needs to provide that.

Need to talk to Identity system developers (OpenID, Cardspace, etc) and figure out how Firefox can better support those mechanisms.
Talk to people doing OpenSource CardSpace implementations and find out what's needed to support those other providers.
Beltzner to start a discussion thread about this in dev.planning.
Mconnor to write up a spec for "way to do login through chrome rather than through a web page".

"Alert user when they're providing info on a suspicious website"
- This has been removed from the PRD but has been flagged as warranting follow up investigation. Should this be a Labs project? Could be related to password management.
"Private Browsing Mode"
- Someone needs to investigate liability issues related to this feature and how we "sell" it.
"Blacklisting of malicious sites"
- Definition of "malware" is required -- needs to be thought through very carefully.

"Play all popular media formats when plugins are installed"
- Follow up required here to investigate bundling possibilities and options.
"Plugin crashes should not crash the entire application"
- Must be added to Moz2 tracking
Improve download handling
- Requires support from Gecko side, so this has to be discussed with the Platform team.
"Download manager can be extended in a way that feels tightly integrated"
- Requires further investigation and refinement
"Microformats"
- Entire section needs to be revisited and possibly reworded with intention of deemphasizing "microformats" and focusing on a more generalizable system of inferred pieces of data, metadata, other forms of structured information on a page.
- All FRs/NFRs need to be revisited with this in mind
RSS enclosure handling
- Further investigation and discussion required here as it's currently a mess and the existing PRD doesn't deal with it at all.

"Rich search results (needs to be more clearly defined)"
- This needs to be more clearly defined and turned into a set of actionable PRD line items.

Mconnor to provide Visio for help/support flow
We need a separate effort outside of the Firefox3 scope towards investigating and doing something about user help and support. This doesn't necessarily have to be absolutely tied to the product.
Larger project is out of band for Firefox 3 and needs to be taken on as a separate independent project.
We need someone who can own this entire world.
"Showcase breadth of customization options"
- Requires clearer definition in consultation with Beltzner
"Crash reporting"
- Requires follow up and refinement

MSI priority needs to be verified
Airbag team needs to be involved with fleshing out Airbag PRD items where/if required.
"Windows Group Policy support"
- More detail required as it currently has no concrete FRs
"Vista Parental Controls support"
- We do not currently know what's entirely involved with this, needs to be investigated in more depth. Specific FRs required.
Dbaron to come up with a list of specific Linux issues that should be dealt with in Firefox 3 and those will be added to the PRD as FR line items.
"Version detection for Windows - Vista vs XP since we may want to have a different theme for each. Installation configuration piece."
- This is largely undefined and was not expanded upon further in the meeting. See meeting notes for info.

"UI for Export"
- Needs to be discussed and decided. If UI is required, must be added to the PRD.
"Places organizer redesign"
- Too vague to be useful. Needs to be investigated in more depth for actual requirements which should then be added to the PRD.
Live Bookmark vs New Subscription user agent string? Basil's question requires follow up.