Places:Design Overview: Difference between revisions

Jump to navigation Jump to search
Line 35: Line 35:
* Flexible Query System
* Flexible Query System
* Clean Architecture for ease of code reuse and maintainability
* Clean Architecture for ease of code reuse and maintainability
== Background ==
Studies from the late 1990s show that while revisitations of pages previously seen counted for roughly 39% of all page navigations (see [http://scholar.google.com/ Google Scholar]), Bookmarks and History usage was low (1-3%), despite the fact that roughly 20% of those revisitations were to pages seen > 10 URLs ago (and thus outside the usefulness range of the Back button or menu).
Autocomplete in the URL bar is a useful tool but fails to address some common desires when looking up visited pages. There is a gulf between the capabilities of that tool, the capabilities of the Bookmarks and History systems today, and the desired capabilities of those systems.
== Use Cases ==
* [[Places:History Use Cases]]
* [[Bookmarks Use Cases]] (not specific to places)
== Functional Requirements ==
The original requirements for Places in Firefox 3 are detailed in the [[Firefox3/Product_Requirements_Document#Places|Firefox 3 PRD]]


== Front End Architecture ==
== Front End Architecture ==
Confirmed users, Bureaucrats and Sysops emeriti
2,088

edits

Navigation menu