Tabbed Browsing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (Fix "places" link)
m (→‎Goals & Objectives: REALLY fix the places link)
Line 11: Line 11:
# Identify usability landmines surrounding tabbed browsing
# Identify usability landmines surrounding tabbed browsing
# Ensure compatibility with web applications (window/tab targeting)
# Ensure compatibility with web applications (window/tab targeting)
# Find ways to optimize behaviour even more, in sync with [[Places Places]]
# Find ways to optimize behaviour even more, in sync with [[Places]]


== Planned Milestones ==
== Planned Milestones ==

Revision as of 02:49, 3 December 2005

Please comment in the Talk page (use the Discussion tab above)

* This is a stub and will be expanded in the near future

Tracked by: bug 318168

  • this bug would be used to track status, target, owner and various deliverables

Goals & Objectives

To drive tabbed browsing by default for Firefox 2.

  1. Identify usability landmines surrounding tabbed browsing
  2. Ensure compatibility with web applications (window/tab targeting)
  3. Find ways to optimize behaviour even more, in sync with Places

Planned Milestones

xxxx/xx/xx TBD

Overview

Tabbed browsing is one of the most popular features in Firefox, and as users are exposed they react most favourably once past the learning curve. We want to improve tabbed browsing so that it can be the default for all users, in a friendly and intuitive manner.

Background

There is a considerable amount of debate over the "best" setup for tabbed browsing, and indeed there are numerous extensions that implement various modifications to the default behaviour. We need to conduct a significant amount of study in order to identify the best solution for all users and improve our experience based on those results.

Use Cases

  1. Hardcore tabbed browsing user (10-20 tabs at once, overflows tab bar)
  2. Confident consumer, sometimes uses multiple tabs, primarily single-track browsing
  3. Novice, tabs are a means to avoid managing multiple window.

Functional Requirements

  1. Ease of Use
  2. Best combination of intuitive and optimized behaviours

Optional:

  1. Able to undo tab closing (timed cleanup)

Plans & Design Documents

API Changes Required

  • link targeting of tabs needs to be fixed
  • tabbrowser may have additional methods

Impact

The current design impacts the following areas of development

Integration points with bookmarks and multiple homepages

Extensions

Localization

Update

  • n/a

See Also

Discussion & Implications

Caveats / What We've Tried Before

Security Implications

Privacy Considerations