Talk:Firefox3/Firefox Requirements

Q: What do FR and NFR mean?
A: FR means Functional Requirement, NFR means Non-Functional Requirement.
FR - Requirements define the internal workings, behavior or functionality
NFR - Requirements which impose constraints on the design or implementation (such as performance, security, quality standards, or design constraints).

Px: User interface for creating microformatted content. -faaborg

Feedback here is a lot more of a pain than in a newsgroup or mailing list. --Bzbarsky 19:00, 11 January 2007 (PST)

The "Audience" section (section 2.3) is a little confusing. In particular, it seems to say that "Unlike Microsoft Internet Explorer, Opera and Apple Safari our product is open, secure, intuitive, customizable, privacy-sensitive and innovative". At least that was my initial impression from section 2.3.1. On third reading or so I decided this probably is not the impression this text is trying to convey, but that's what it reads like at first glance. --Bzbarsky 19:00, 11 January 2007 (PST)

Sections 2.3 and 2.4 make a number of statements that I would disagree with pretty strongly. Are these meant to be statements of existing facts, or statements of what we're striving towards? I sincerely hope the latter, because they're pretty false right now. --Bzbarsky 19:00, 11 January 2007 (PST)

What exactly does "# FR: remove local MIME type database for local applications" mean? --Bzbarsky 19:00, 11 January 2007 (PST)

"# NFR: plugin crashes should not crash the entire application " is not likely to happent at this point, in my opinion. Not for Gecko 1.9, not unless you want to drop something else. --Bzbarsky 19:00, 11 January 2007 (PST)

"# FR: pages should break without dividing paragraphs" meaning what? Actually implementing that sounds pretty unfortunate... --Bzbarsky 19:00, 11 January 2007 (PST)

"# FR: print layout should look like rendered layout " again, meaning what? --Bzbarsky 19:00, 11 January 2007 (PST)

"# NFR: printed material should match user expectations " again, meaning what? For example, how do we plan to figure out what user expectations are? What do we do when those expectations collide with the site author expectations and/or the relevant specs? --Bzbarsky 19:00, 11 January 2007 (PST)

A useful NFR for printing, imo, would be "Make the printout look the way a good typesetter would make it look, within the constraints imposed by the site's styling". Or at least that's what we should strive for, I think. --Bzbarsky 19:00, 11 January 2007 (PST)

"* FR: remove client-side documentation and replace with links to online documentation " -- Please leave documentation related to getting access to the network (proxies, etc) client-side (for reasons that should be obvious). --Bzbarsky 19:00, 11 January 2007 (PST)

"Handling of back/forward with POST" -- We already do the FRs listed here, insofar as the site doesn't request that we forget the data. So I'm not sure what these are supposed to be about. The NFR is a good one -- we should have an error page for that instead. --Bzbarsky 19:00, 11 January 2007 (PST)

Where do roaming profiles fit in here, if at all? I find not being able to share bookmarks between home from work one of the most annoying things about my daily browsing experience... ;) --Bzbarsky 19:00, 11 January 2007 (PST)