Tabbed Browsing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 7: Line 7:


= Goals & Objectives =
= Goals & Objectives =
Lorem ipsum dolor sit amet, consectetuer adipiscing elit.  
To drive tabbed browsing by default for Firefox 2.
# Integer eget neque.
 
# Ut pulvinar, nisl ut dapibus euismod, dolor mi aliquam metus.
# Identify usability landmines surrounding tabbed browsing
# Sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.
# Ensure compatibility with web applications (window/tab targeting)
# Find ways to optimize behaviour even more, in sync with [Places Places]


== Planned Milestones ==
== Planned Milestones ==
{| border="0" cellpadding="3" width="100%"
{| border="0" cellpadding="3" width="100%"
|-
|-
! align=right valign=top width="10%" | 01/12/2005
! align=right valign=top width="10%" | xxxx/xx/xx
| This
| TBD
That
|-
! align=right valign=top width="10%" | 08/12/2005
| The other thing
And yet another thing
|-
|-
|}
|}
Line 32: Line 28:


== Use Cases ==
== Use Cases ==
# Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
# Hardcore tabbed browsing user (10-20 tabs at once, overflows tab bar)
# Integer eget neque.
# Confident consumer, sometimes uses multiple tabs, primarily single-track browsing
# Ut pulvinar, nisl ut dapibus euismod, dolor mi aliquam metus, sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.
# Novice, tabs are a means to avoid managing multiple window.


== Functional Requirements ==
== Functional Requirements ==
# Primi
# Ease of Use
# Secondi
# Best combination of intuitive and optimized behaviours
# Dolce
 
Optional:
# Able to undo tab closing (timed cleanup)


== Plans & Design Documents ==
== Plans & Design Documents ==
Line 48: Line 46:


== API Changes Required ==
== API Changes Required ==
* this one
* link targeting of tabs needs to be fixed
* that one
* tabbrowser may have additional methods


== Impact ==
== Impact ==
The current design impacts the following areas of development ...
The current design impacts the following areas of development  
 
Integration points with bookmarks and multiple homepages


=== Extensions ===
=== Extensions ===

Revision as of 22:32, 29 November 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 Places]

Planned Milestones

xxxx/xx/xx TBD

Overview

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer eget neque. Ut pulvinar, nisl ut dapibus euismod, dolor mi aliquam metus, sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.

Background

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer eget neque. Ut pulvinar, nisl ut dapibus euismod, dolor mi aliquam metus, sed ultrices sem erat eget metus. Vestibulum blandit elementum nibh.

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