Tabbed Browsing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(+Obsolete flag)
 
(16 intermediate revisions by 9 users not shown)
Line 1: Line 1:
{{RELEASE_MANAGEMENT_OBSOLETE}}
''Please comment in the Talk page (use the Discussion tab above)''
''Please comment in the Talk page (use the Discussion tab above)''


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


Tracked by: [https://bugzilla.mozilla.org/show_bug.cgi?id=40000 bug 40000]
Tracked by: [https://bugzilla.mozilla.org/show_bug.cgi?id=318168 bug 318168]
*''this bug would be used to track status, target, owner and various deliverables''
*''this bug would be used to track status, target, owner and various deliverables''


= 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]]


== 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%" | Alpha 1
| This
| Tab overflow
That
| basic functional spec done
|-
|
| Undo tab close
| basic impl done, needs cleanup
|-
|-
! align=right valign=top width="10%" | 08/12/2005
|  
| The other thing
| Closebuttons on tabs
And yet another thing
| Done, fixing regressions
|-
|-
! align=right valign=top width="10%" | Alpha 2
| Browsermessage API enhancements
| Spec needed
|}
|}


= Overview =
= 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.
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 ==
== 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.
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 ==
== User Audiences ==
# 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 windows.


== 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 ==
* [[/User Interface Design|User Interface Design]]
* [[Tabbed_Browsing/User Interface Design|User Interface Design]]
* [[/Code Design|Code Design]]
* [[/Code Design|Code Design]]
* [[/Test Plan|Test Plan]]
* [[/Test Plan|Test Plan]]
Line 48: Line 59:


== API Changes Required ==
== API Changes Required ==
* this one
* link targeting of tabs needs to be fixed ([https://bugzilla.mozilla.org/show_bug.cgi?id=323810 bug 323810])
* 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 ===
Line 64: Line 77:


= Discussion & Implications =
= Discussion & Implications =
This issue was brought up late in the Firefox 1.5 development cycle, and some good discussion was generated which detailed a lot of the issues and explored several options.
See [[Link_Targeting|this wiki page on tabbed browsing behavior]] as well as [https://bugzilla.mozilla.org/show_bug.cgi?id=308396 bug 308396] for some of that discussion.
There is a cumulative list at of tabbed browsing issues at [[Tabbed_Browsing/User_Interface_Design/Tab_Overflow]] and on its talk page [[Talk:Tabbed_Browsing/User_Interface_Design/Tab_Overflow]]


== Caveats / What We've Tried Before ==
== Caveats / What We've Tried Before ==

Latest revision as of 14:14, 2 January 2019

Warning: The content of this page is obsolete and kept for archiving purposes of past processes.

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

Alpha 1 Tab overflow basic functional spec done
Undo tab close basic impl done, needs cleanup
Closebuttons on tabs Done, fixing regressions
Alpha 2 Browsermessage API enhancements Spec needed

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.

User Audiences

  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 windows.

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 (bug 323810)
  • 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

This issue was brought up late in the Firefox 1.5 development cycle, and some good discussion was generated which detailed a lot of the issues and explored several options.

See this wiki page on tabbed browsing behavior as well as bug 308396 for some of that discussion.

There is a cumulative list at of tabbed browsing issues at Tabbed_Browsing/User_Interface_Design/Tab_Overflow and on its talk page Talk:Tabbed_Browsing/User_Interface_Design/Tab_Overflow

Caveats / What We've Tried Before

Security Implications

Privacy Considerations