<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.mozilla.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Caleb</id>
	<title>MozillaWiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.mozilla.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Caleb"/>
	<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/Special:Contributions/Caleb"/>
	<updated>2026-11-16T14:44:42Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.17</generator>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Firefox:Download_Manager:Scratch_Pad&amp;diff=19557</id>
		<title>Firefox:Download Manager:Scratch Pad</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Firefox:Download_Manager:Scratch_Pad&amp;diff=19557"/>
		<updated>2005-11-06T20:01:40Z</updated>

		<summary type="html">&lt;p&gt;Caleb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;When the user is downloading, we should only display a link to pause a downloading entry. The cancel link shouldn&#039;t be displayed on a downloading entry since the user might accidentally click on it and cancel the download. Instead Cancel should only appear on a paused entry.&lt;br /&gt;
&lt;br /&gt;
However, all of the download control commands (pause/resume, cancel and restart) should be available on the context menu and the user should be allowed to select multiple entries and apply actions on them.&lt;br /&gt;
&lt;br /&gt;
There should at least be an option in about:config to restore the Cancel button, since to many Firefox users this is not a major problem.&lt;br /&gt;
&lt;br /&gt;
One more important thing: Do NOT restart the download of a currently downloading entry if the user clicks a link and saves it _again_. For example, start downloading file A. Click on the link to download A again, save it, and your download will restart from 0%! This should be handled in a better way... (Maybe changing the target path of the currently downloading file?) --[[User:Caleb|Caleb]] 12:01, 6 Nov 2005 (PST)&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Feed_Handling:User_Interface&amp;diff=13719</id>
		<title>Feed Handling:User Interface</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Feed_Handling:User_Interface&amp;diff=13719"/>
		<updated>2005-11-04T09:43:59Z</updated>

		<summary type="html">&lt;p&gt;Caleb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Background ===&lt;br /&gt;
&lt;br /&gt;
The FeedView RSS pretty print extension has been checked in for Firefox 1.5. Numerous bugs have been pointed out in the feature however and the UI is not up to Firefox quality standards. All of this resulted in FeedView being backed out for 1.5 and targetted for the 2.0 release.&lt;br /&gt;
&lt;br /&gt;
The main tracking bug for this feature is [https://bugzilla.mozilla.org/show_bug.cgi?id=302121 bug 302121].&lt;br /&gt;
&lt;br /&gt;
=== What Is Needed ===&lt;br /&gt;
&lt;br /&gt;
An audit and investigation of our existing RSS features and a UI that integrates them nicely. &lt;br /&gt;
&lt;br /&gt;
=== Required Features ===&lt;br /&gt;
&lt;br /&gt;
* Discoverable UI for showing and bookmarking feeds&lt;br /&gt;
* Ability to bookmark feed for easy use&lt;br /&gt;
* Attractive presentation of feeds when viewed in the browser&lt;br /&gt;
* RSS(all versions) and ATOM support&lt;br /&gt;
&lt;br /&gt;
=== UI Design ===&lt;br /&gt;
&lt;br /&gt;
When a page with an appropriate &amp;lt;link rel&amp;gt; tag is discovered, place this icon in the location bar:&lt;br /&gt;
&lt;br /&gt;
http://www.bengoodger.com/software/mb/bookmarks/iconandlocationbar.png&lt;br /&gt;
&lt;br /&gt;
When the icon is clicked, show a pretty print of the feed. If there is more than one *TYPE* of RSS feed, &amp;quot;pick the best format&amp;quot; and show that. If there are multiple links with the same format, assume there are multiple feeds (e.g. a blog feed vs. a comments feed) and show a menu, e.g.:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 [@v]&lt;br /&gt;
+----------------------------+&lt;br /&gt;
| Show News.com Feed         |&lt;br /&gt;
| Show Business Stories Feed |&lt;br /&gt;
| Show Security Stories Feed |&lt;br /&gt;
| Show Internet Fads Feed    |&lt;br /&gt;
+----------------------------+&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The pretty print should be laid out like so:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
+-------------------------------------------------------+&lt;br /&gt;
| FEED TITLE                                            |&lt;br /&gt;
+-------------------------------------------------------+&lt;br /&gt;
  &lt;br /&gt;
  [-] Entry Title ======================  [Expand All] &lt;br /&gt;
                                          [Collapse All]&lt;br /&gt;
  entry text entry text entry text entry   &lt;br /&gt;
  entry text entry text entry text entry&lt;br /&gt;
  entry text entry text entry text entry  Add Live Bookmark:&lt;br /&gt;
  entry text entry text entry text entry  Name:&lt;br /&gt;
  entry text entry text entry text entry  [                ] &amp;lt;-- name, prefilled&lt;br /&gt;
  entry text entry text entry text entry  In:&lt;br /&gt;
  entry text entry ...                    [ Bookmarks Bar:^] &amp;lt;-- folder selector&lt;br /&gt;
                                                     ( Add )&lt;br /&gt;
  [-] Entry Title ======================&lt;br /&gt;
&lt;br /&gt;
  entry text entry text entry text entry&lt;br /&gt;
  entry text entry text entry text entry&lt;br /&gt;
  entry text entry text entry text entry&lt;br /&gt;
  entry text entry ...&lt;br /&gt;
&lt;br /&gt;
  [-] Entry Title ======================&lt;br /&gt;
&lt;br /&gt;
  entry text entry text entry text entry&lt;br /&gt;
  entry text entry text entry text entry&lt;br /&gt;
  entry text entry ...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Problems With Current Implementation ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;With the status bar selector:&#039;&#039;&#039;&lt;br /&gt;
* Not discoverable&lt;br /&gt;
* No keyboard shortcut for creating a Live Bookmark&lt;br /&gt;
* Shows menu even when there&#039;s only one feed, or multiple formats to the same feed&lt;br /&gt;
* Defaults saving bookmark into Bookmarks list - Feeds are more constant use items, should default to saving into Bookmarks Toolbar folder&lt;br /&gt;
* Defaults bookmark title to be the &amp;quot;title&amp;quot; attribute of the &amp;lt;link rel&amp;gt; tag instead of the feed title&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;With the pretty print&#039;&#039;&#039;&lt;br /&gt;
* Excerpt length selector is useless (and flickers badly, even on capable hardware) - should just have a &#039;headings only&#039; vs. &#039;headings+excerpts&#039; view&lt;br /&gt;
* No easy way to add a bookmark other than the non-discoverable status bar icon&lt;br /&gt;
* Looks just like Safari but with different colors - does not feel firefox or mozilla-like: should engage visual design team to do a better style sheet&lt;br /&gt;
* various rendering errors (escaped HTML, &amp;lt;a hrefs&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
* move feed discovery icon into location bar, like the lock icon&lt;br /&gt;
* make the discovery icon intelligent and automatically pick the best feed from a variety of identical-feed-different-format choices&lt;br /&gt;
* make the discovery icon show the pretty print&lt;br /&gt;
* make link clicks on feed urls show the pretty print&lt;br /&gt;
* make the pretty print have an attractive, mozilla-like style&lt;br /&gt;
* ditch the length selector and replace with headings only vs. headings+excerpts&lt;br /&gt;
** maybe use an &amp;quot;expand&amp;quot; vs &amp;quot;collapse&amp;quot; metaphor here instead, so &amp;quot;expand all&amp;quot; and &amp;quot;collapse all&amp;quot; with [+] / [-] buttons next to each feed&lt;br /&gt;
* add a prominent &amp;quot;bookmark feed&amp;quot; box that default bookmarks onto links toolbar with folder selector.&lt;br /&gt;
** should use the feed title as the default name for the bookmark&lt;br /&gt;
* fix various rendering bugs in the pretty print&lt;br /&gt;
** HTML escaped entities ([https://bugzilla.mozilla.org/show_bug.cgi?id=303206 bug 303206])&lt;br /&gt;
** render HTML links and formatting ([https://bugzilla.mozilla.org/show_bug.cgi?id=302749 bug 302749])&lt;br /&gt;
&lt;br /&gt;
=== TBD &amp;amp; Open Questions ===&lt;br /&gt;
* Should all bookmarked RSS/Atom files be treated as Live Bookmarks automatically?&lt;br /&gt;
* Should we consider the possibilty that there may be multiple feed types with different contents but the same filename?&lt;br /&gt;
* Have we talked about including a &amp;quot;what is this&amp;quot; type of thing on the right side next to the &amp;quot;Add Live Bookmark&amp;quot; section?  IE7 does this, and I think it&#039;d be good to make sure users know what exactly they are looking at.&lt;br /&gt;
* What will happen when the location bar is hidden by the user?&lt;br /&gt;
* What indication is available to notify that a page has some kind of feed(s)&lt;br /&gt;
&lt;br /&gt;
=== User Comments ===&lt;br /&gt;
* There&#039;s one major flaw in Live Bookmarks, and that is the lack of notifications of new content in the feed. There should be a way of notifying you that the bookmarked feeds have new (unread) content both in the toolbar, and possibly via dowload-manager-like alerts (for bookmarks that are not visible on the toolbar). --[[User:Caleb|Caleb]] 01:43, 4 Nov 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* With the growing amount of blogs/feeds out there people end up adding lots of live feeds to their bookmarks toolbar, which reduces the amount of space for &amp;quot;real&amp;quot; bookmarks in the toolbar. Maybe (at some point in the future, or in FF3) there should be some kind of a different mechanism for managing live bookmarks/feeds/etc..? --[[User:Caleb|Caleb]] 01:43, 4 Nov 2005 (PST)&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Feed_Handling:User_Interface&amp;diff=13252</id>
		<title>Feed Handling:User Interface</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Feed_Handling:User_Interface&amp;diff=13252"/>
		<updated>2005-11-04T09:43:35Z</updated>

		<summary type="html">&lt;p&gt;Caleb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Background ===&lt;br /&gt;
&lt;br /&gt;
The FeedView RSS pretty print extension has been checked in for Firefox 1.5. Numerous bugs have been pointed out in the feature however and the UI is not up to Firefox quality standards. All of this resulted in FeedView being backed out for 1.5 and targetted for the 2.0 release.&lt;br /&gt;
&lt;br /&gt;
The main tracking bug for this feature is [https://bugzilla.mozilla.org/show_bug.cgi?id=302121 bug 302121].&lt;br /&gt;
&lt;br /&gt;
=== What Is Needed ===&lt;br /&gt;
&lt;br /&gt;
An audit and investigation of our existing RSS features and a UI that integrates them nicely. &lt;br /&gt;
&lt;br /&gt;
=== Required Features ===&lt;br /&gt;
&lt;br /&gt;
* Discoverable UI for showing and bookmarking feeds&lt;br /&gt;
* Ability to bookmark feed for easy use&lt;br /&gt;
* Attractive presentation of feeds when viewed in the browser&lt;br /&gt;
* RSS(all versions) and ATOM support&lt;br /&gt;
&lt;br /&gt;
=== UI Design ===&lt;br /&gt;
&lt;br /&gt;
When a page with an appropriate &amp;lt;link rel&amp;gt; tag is discovered, place this icon in the location bar:&lt;br /&gt;
&lt;br /&gt;
http://www.bengoodger.com/software/mb/bookmarks/iconandlocationbar.png&lt;br /&gt;
&lt;br /&gt;
When the icon is clicked, show a pretty print of the feed. If there is more than one *TYPE* of RSS feed, &amp;quot;pick the best format&amp;quot; and show that. If there are multiple links with the same format, assume there are multiple feeds (e.g. a blog feed vs. a comments feed) and show a menu, e.g.:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 [@v]&lt;br /&gt;
+----------------------------+&lt;br /&gt;
| Show News.com Feed         |&lt;br /&gt;
| Show Business Stories Feed |&lt;br /&gt;
| Show Security Stories Feed |&lt;br /&gt;
| Show Internet Fads Feed    |&lt;br /&gt;
+----------------------------+&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The pretty print should be laid out like so:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
+-------------------------------------------------------+&lt;br /&gt;
| FEED TITLE                                            |&lt;br /&gt;
+-------------------------------------------------------+&lt;br /&gt;
  &lt;br /&gt;
  [-] Entry Title ======================  [Expand All] &lt;br /&gt;
                                          [Collapse All]&lt;br /&gt;
  entry text entry text entry text entry   &lt;br /&gt;
  entry text entry text entry text entry&lt;br /&gt;
  entry text entry text entry text entry  Add Live Bookmark:&lt;br /&gt;
  entry text entry text entry text entry  Name:&lt;br /&gt;
  entry text entry text entry text entry  [                ] &amp;lt;-- name, prefilled&lt;br /&gt;
  entry text entry text entry text entry  In:&lt;br /&gt;
  entry text entry ...                    [ Bookmarks Bar:^] &amp;lt;-- folder selector&lt;br /&gt;
                                                     ( Add )&lt;br /&gt;
  [-] Entry Title ======================&lt;br /&gt;
&lt;br /&gt;
  entry text entry text entry text entry&lt;br /&gt;
  entry text entry text entry text entry&lt;br /&gt;
  entry text entry text entry text entry&lt;br /&gt;
  entry text entry ...&lt;br /&gt;
&lt;br /&gt;
  [-] Entry Title ======================&lt;br /&gt;
&lt;br /&gt;
  entry text entry text entry text entry&lt;br /&gt;
  entry text entry text entry text entry&lt;br /&gt;
  entry text entry ...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Problems With Current Implementation ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;With the status bar selector:&#039;&#039;&#039;&lt;br /&gt;
* Not discoverable&lt;br /&gt;
* No keyboard shortcut for creating a Live Bookmark&lt;br /&gt;
* Shows menu even when there&#039;s only one feed, or multiple formats to the same feed&lt;br /&gt;
* Defaults saving bookmark into Bookmarks list - Feeds are more constant use items, should default to saving into Bookmarks Toolbar folder&lt;br /&gt;
* Defaults bookmark title to be the &amp;quot;title&amp;quot; attribute of the &amp;lt;link rel&amp;gt; tag instead of the feed title&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;With the pretty print&#039;&#039;&#039;&lt;br /&gt;
* Excerpt length selector is useless (and flickers badly, even on capable hardware) - should just have a &#039;headings only&#039; vs. &#039;headings+excerpts&#039; view&lt;br /&gt;
* No easy way to add a bookmark other than the non-discoverable status bar icon&lt;br /&gt;
* Looks just like Safari but with different colors - does not feel firefox or mozilla-like: should engage visual design team to do a better style sheet&lt;br /&gt;
* various rendering errors (escaped HTML, &amp;lt;a hrefs&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
=== Recommendations ===&lt;br /&gt;
* move feed discovery icon into location bar, like the lock icon&lt;br /&gt;
* make the discovery icon intelligent and automatically pick the best feed from a variety of identical-feed-different-format choices&lt;br /&gt;
* make the discovery icon show the pretty print&lt;br /&gt;
* make link clicks on feed urls show the pretty print&lt;br /&gt;
* make the pretty print have an attractive, mozilla-like style&lt;br /&gt;
* ditch the length selector and replace with headings only vs. headings+excerpts&lt;br /&gt;
** maybe use an &amp;quot;expand&amp;quot; vs &amp;quot;collapse&amp;quot; metaphor here instead, so &amp;quot;expand all&amp;quot; and &amp;quot;collapse all&amp;quot; with [+] / [-] buttons next to each feed&lt;br /&gt;
* add a prominent &amp;quot;bookmark feed&amp;quot; box that default bookmarks onto links toolbar with folder selector.&lt;br /&gt;
** should use the feed title as the default name for the bookmark&lt;br /&gt;
* fix various rendering bugs in the pretty print&lt;br /&gt;
** HTML escaped entities ([https://bugzilla.mozilla.org/show_bug.cgi?id=303206 bug 303206])&lt;br /&gt;
** render HTML links and formatting ([https://bugzilla.mozilla.org/show_bug.cgi?id=302749 bug 302749])&lt;br /&gt;
&lt;br /&gt;
=== TBD &amp;amp; Open Questions ===&lt;br /&gt;
* Should all bookmarked RSS/Atom files be treated as Live Bookmarks automatically?&lt;br /&gt;
* Should we consider the possibilty that there may be multiple feed types with different contents but the same filename?&lt;br /&gt;
* Have we talked about including a &amp;quot;what is this&amp;quot; type of thing on the right side next to the &amp;quot;Add Live Bookmark&amp;quot; section?  IE7 does this, and I think it&#039;d be good to make sure users know what exactly they are looking at.&lt;br /&gt;
* What will happen when the location bar is hidden by the user?&lt;br /&gt;
* What indication is available to notify that a page has some kind of feed(s)&lt;br /&gt;
&lt;br /&gt;
=== User Comments ===&lt;br /&gt;
* There&#039;s one major flaw in Live Bookmarks, and that is the lack of notifications of new content in the feed. There should be a way of notifying you that the bookmarked feeds have new (unread) content both in the toolbar, and possibly via dowload-manager-like alerts (for bookmarks that are not visible on the toolbar).&lt;br /&gt;
&lt;br /&gt;
* With the growing amount of blogs/feeds out there people end up adding lots of live feeds to their bookmarks toolbar, which reduces the amount of space for &amp;quot;real&amp;quot; bookmarks in the toolbar. Maybe (at some point in the future, or in FF3) there should be some kind of a different mechanism for managing live bookmarks/feeds/etc..?&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Download_Size&amp;diff=16605</id>
		<title>Download Size</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Download_Size&amp;diff=16605"/>
		<updated>2005-11-02T06:03:58Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Background */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Download Size =&lt;br /&gt;
&lt;br /&gt;
== Background ==&lt;br /&gt;
&lt;br /&gt;
Download size is an important factor in adoption. Keeping the download size small, especially below a mental barrier like 5.0 MB keeps Firefox in the class as &amp;quot;simple utility applications&amp;quot; and is downloaded without as much hesitation by users. It also allows clever marketing ala Asa&#039;s &amp;quot;It&#039;s like downloading an MP3&amp;quot;&lt;br /&gt;
&lt;br /&gt;
To maintain a trim download size as new features and compiler requirements arrive, we must develop strategies to make our existing code better and cleaner. &lt;br /&gt;
&lt;br /&gt;
Keeping a compact download size should be on the mind of every engineer on the Firefox project, just like accessibility and internationalization.&lt;br /&gt;
&lt;br /&gt;
== Studies ==&lt;br /&gt;
&lt;br /&gt;
== Strategies ==&lt;br /&gt;
&lt;br /&gt;
* trim down InternetSearchService&lt;br /&gt;
* remove unnecessary xpinstall components&lt;br /&gt;
* better 7zip tuning&lt;br /&gt;
* trim the installer (currently rather bloated)&lt;br /&gt;
* xulrunner installer that downloads firefox.xap&lt;br /&gt;
* remove more unnecessary chrome and xpfe cruft (e.g. browserinstance)&lt;br /&gt;
* etc.&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Gecko:Layout_Improvements&amp;diff=12442</id>
		<title>Gecko:Layout Improvements</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Gecko:Layout_Improvements&amp;diff=12442"/>
		<updated>2005-09-14T21:06:24Z</updated>

		<summary type="html">&lt;p&gt;Caleb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This started from [[User:Dbaron]]&#039;s list, and some probably belong in [[Gecko:Content Team Minutes]] instead.&lt;br /&gt;
&lt;br /&gt;
A. Reflow refactoring&lt;br /&gt;
&lt;br /&gt;
B. Global object proxying so that one global object per document -- maybe proxying for frame.window rather than subitituting during load?&lt;br /&gt;
&lt;br /&gt;
C. Stylesheet loading not blocking parser.&lt;br /&gt;
&lt;br /&gt;
D. [[Mozilla2:Units]] Units rewrite&lt;br /&gt;
&lt;br /&gt;
E. Make XML content sink incremental (maybe switch to libxml2 at same time)&lt;br /&gt;
&lt;br /&gt;
F. Fix incremental page loading timer + paint supression nightmare (depends on (B) and (C)).&lt;br /&gt;
&lt;br /&gt;
G. Adaptive zoom (depends on (D)).&lt;br /&gt;
&lt;br /&gt;
H. Make Print Preview use its own window.&lt;br /&gt;
&lt;br /&gt;
I. Focus mess - make it a tree&lt;br /&gt;
&lt;br /&gt;
J. (related to (I)) - have a better notion, for embedding and for making tabbrowser less hacky -- of having a docshell hidden (no resize reflows, no focus, no gif animating, etc.)&lt;br /&gt;
&lt;br /&gt;
K. Make hidden views mean something, perhaps?&lt;br /&gt;
&lt;br /&gt;
L. Frame constructor refactoring and movement towards extensibility. Maybe put style contexts on content.&lt;br /&gt;
&lt;br /&gt;
M. Docshell cleanup (related to (J)).&lt;br /&gt;
&lt;br /&gt;
N. [[Gecko:NativeWidgetOverhaul]] Move to one widget per top-level window --- no child widgets.&lt;br /&gt;
&lt;br /&gt;
O. Eliminate the view manager and the separate view tree; just work off the frame tree and move all the functionality to the presshell.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;s&amp;gt;P. [[Gecko:Event Dispatching Coordinates]] Make the passing of event coordinates more consistent and sane.&amp;lt;/s&amp;gt;&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=DocShell&amp;diff=11931</id>
		<title>DocShell</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=DocShell&amp;diff=11931"/>
		<updated>2005-08-13T05:42:34Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Current plans for docshell */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Docshell Documentation =&lt;br /&gt;
&lt;br /&gt;
The goal of this page is to serve as a dumping/organization ground for docshell&lt;br /&gt;
docs.  When someone finds out something, it should be added here in a&lt;br /&gt;
reasonable way.  By the time this gets unwieldy, hopefully we will have enough&lt;br /&gt;
material for several actual docs on what docshell does and why.&lt;br /&gt;
&lt;br /&gt;
Some of these sections need writing, and we may need other sections... Feel free to rearrange as needed&lt;br /&gt;
&lt;br /&gt;
* [http://www.mozilla.org/projects/embedding/docshell.html About] (What actually is docshell?)&lt;br /&gt;
* [[DocShell:Fastback|How fastback is implemented]]&lt;br /&gt;
&lt;br /&gt;
== Interfaces Implemented by Docshell ==&lt;br /&gt;
&lt;br /&gt;
Docshell + webshell implement the following interfaces&lt;br /&gt;
&lt;br /&gt;
Webshell:&lt;br /&gt;
&lt;br /&gt;
* nsIWebShell                 [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShell.h#75 LXR]&lt;br /&gt;
* nsIWebShellContainer        [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShell.h#66 LXR]&lt;br /&gt;
* nsIWebShellServices         [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShellServices.h#52 LXR]&lt;br /&gt;
* nsILinkHandler              [http://lxr.mozilla.org/mozilla/source/webshell/public/nsILinkHandler.h#70 LXR]&lt;br /&gt;
* nsIClipboardCommands (why?) [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIClipboardCommands.idl#42 LXR]&lt;br /&gt;
&lt;br /&gt;
Docshell:&lt;br /&gt;
&lt;br /&gt;
* nsIDocShell                 [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShell.idl#68 LXR]&lt;br /&gt;
* nsIDocShellTreeItem         [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellTreeItem.idl#45 LXR]&lt;br /&gt;
* nsIDocShellTreeNode         [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellTreeNode.idl#44 LXR]&lt;br /&gt;
* nsIDocShellHistory          [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellHistory.idl#42 LXR]&lt;br /&gt;
* nsIWebNavigation            [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIWebNavigation.idl#42 LXR]&lt;br /&gt;
* nsIBaseWindow               [http://lxr.mozilla.org/mozilla/source/widget/public/nsIBaseWindow.idl#51 LXR]&lt;br /&gt;
* nsIScrollable               [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIScrollable.idl#42 LXR]&lt;br /&gt;
* nsITextScroll               [http://lxr.mozilla.org/mozilla/source/docshell/base/nsITextScroll.idl#43 LXR]&lt;br /&gt;
* nsIDocCharset               [http://lxr.mozilla.org/mozilla/source/intl/chardet/public/nsIDocCharset.idl#41 LXR]&lt;br /&gt;
* nsIContentViewerContainer   [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIContentViewerContainer.idl#43 LXR]&lt;br /&gt;
* nsIInterfaceRequestor       [http://lxr.mozilla.org/mozilla/source/xpcom/base/nsIInterfaceRequestor.idl#42 LXR]&lt;br /&gt;
* nsIScriptGlobalObjectOwner  [http://lxr.mozilla.org/mozilla/source/dom/public/nsIScriptGlobalObjectOwner.h#50 LXR]&lt;br /&gt;
* nsIRefreshURI               [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIRefreshURI.idl#43 LXR]&lt;br /&gt;
* nsIWebProgressListener      [http://lxr.mozilla.org/mozilla/source/uriloader/base/nsIWebProgressListener.idl#47 LXR]&lt;br /&gt;
* nsIEditorDocShell           [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIEditorDocShell.idl#45 LXR]&lt;br /&gt;
* nsIWebPageDescriptor        [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIWebPageDescriptor.idl#38 LXR]&lt;br /&gt;
&lt;br /&gt;
In my view, nsIDocShellTree* and nsIWebShellContainer should all be merged into a single &amp;quot;tree node&amp;quot; interface.  nsIWebShell should merge into nsIDocShell.  nsILinkHandler, not sure.  nsIContentViewerContainer and nsIScriptGlobalObjectOwner, do we really need those?  nsIRefreshURI is probably something to merge into nsIDocShell (or even nsIWebNavigation?).  nsIEditorDocshell also doesn&#039;t really need to be a separate interface.&lt;br /&gt;
&lt;br /&gt;
Then again, do we want to just dump all sorts of stuff onto nsIDocShell?  Not sure about that.  Maybe we should look at who uses nsIDocShell and these other interfaces and why?&lt;br /&gt;
&lt;br /&gt;
== Session history (needs work) ==&lt;br /&gt;
== URI loading (needs work) ==&lt;br /&gt;
== Progress notifications (needs work) ==&lt;br /&gt;
&lt;br /&gt;
== Bugs that could need some Docshell cleanup (needs work) ==&lt;br /&gt;
&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=249751 bug 249751] Links whose onclick closes the window fail to trigger link&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=84833 bug 84833] Calling self.close() right after calling submit() cancels submission&lt;br /&gt;
&lt;br /&gt;
== Current plans for docshell ==&lt;br /&gt;
&lt;br /&gt;
[[DocShell:IRC_Logs]] has some IRC discussions concerning the future direction of docshell and docloader&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Can we eliminate mOSHE/mLSHE in favor of just accessing the shistory&#039;s entry for mIndex/mRequestedIndex?&lt;br /&gt;
&lt;br /&gt;
== Completed Work ==&lt;br /&gt;
&lt;br /&gt;
nsIWebShell removed. Thanks to bz!  -- [http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&amp;amp;module=all&amp;amp;branch=&amp;amp;branchtype=match&amp;amp;dir=&amp;amp;file=&amp;amp;filetype=match&amp;amp;who=&amp;amp;whotype=match&amp;amp;sortby=Date&amp;amp;hours=2&amp;amp;date=explicit&amp;amp;mindate=2005-01-03+14%3A49&amp;amp;maxdate=2005-01-03+14%3A51&amp;amp;cvsroot=%2Fcvsroot Bonsai]&lt;br /&gt;
&lt;br /&gt;
nsDocLoaderImpl ([http://lxr.mozilla.org/mozilla/source/uriloader/base/nsDocLoader.cpp nsDocLoader.cpp]) will be merged into nsDocShell; or rather, nsDocShell will become a subclass of nsDocLoaderImpl (&amp;lt;s&amp;gt;[https://bugzilla.mozilla.org/show_bug.cgi?id=272471 bug 272471]&amp;lt;/s&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
nsIWebShell and nsIWebShellContainer were eliminated (&amp;lt;s&amp;gt;[https://bugzilla.mozilla.org/show_bug.cgi?id=273319 bug 273319]&amp;lt;/s&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;s&amp;gt;[https://bugzilla.mozilla.org/show_bug.cgi?id=261086 bug 261086]&amp;lt;/s&amp;gt; - docshell does not need quite as many things in its GetInterface implementation&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=DocShell&amp;diff=10977</id>
		<title>DocShell</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=DocShell&amp;diff=10977"/>
		<updated>2005-08-13T05:42:07Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Completed Work */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Docshell Documentation =&lt;br /&gt;
&lt;br /&gt;
The goal of this page is to serve as a dumping/organization ground for docshell&lt;br /&gt;
docs.  When someone finds out something, it should be added here in a&lt;br /&gt;
reasonable way.  By the time this gets unwieldy, hopefully we will have enough&lt;br /&gt;
material for several actual docs on what docshell does and why.&lt;br /&gt;
&lt;br /&gt;
Some of these sections need writing, and we may need other sections... Feel free to rearrange as needed&lt;br /&gt;
&lt;br /&gt;
* [http://www.mozilla.org/projects/embedding/docshell.html About] (What actually is docshell?)&lt;br /&gt;
* [[DocShell:Fastback|How fastback is implemented]]&lt;br /&gt;
&lt;br /&gt;
== Interfaces Implemented by Docshell ==&lt;br /&gt;
&lt;br /&gt;
Docshell + webshell implement the following interfaces&lt;br /&gt;
&lt;br /&gt;
Webshell:&lt;br /&gt;
&lt;br /&gt;
* nsIWebShell                 [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShell.h#75 LXR]&lt;br /&gt;
* nsIWebShellContainer        [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShell.h#66 LXR]&lt;br /&gt;
* nsIWebShellServices         [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShellServices.h#52 LXR]&lt;br /&gt;
* nsILinkHandler              [http://lxr.mozilla.org/mozilla/source/webshell/public/nsILinkHandler.h#70 LXR]&lt;br /&gt;
* nsIClipboardCommands (why?) [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIClipboardCommands.idl#42 LXR]&lt;br /&gt;
&lt;br /&gt;
Docshell:&lt;br /&gt;
&lt;br /&gt;
* nsIDocShell                 [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShell.idl#68 LXR]&lt;br /&gt;
* nsIDocShellTreeItem         [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellTreeItem.idl#45 LXR]&lt;br /&gt;
* nsIDocShellTreeNode         [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellTreeNode.idl#44 LXR]&lt;br /&gt;
* nsIDocShellHistory          [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellHistory.idl#42 LXR]&lt;br /&gt;
* nsIWebNavigation            [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIWebNavigation.idl#42 LXR]&lt;br /&gt;
* nsIBaseWindow               [http://lxr.mozilla.org/mozilla/source/widget/public/nsIBaseWindow.idl#51 LXR]&lt;br /&gt;
* nsIScrollable               [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIScrollable.idl#42 LXR]&lt;br /&gt;
* nsITextScroll               [http://lxr.mozilla.org/mozilla/source/docshell/base/nsITextScroll.idl#43 LXR]&lt;br /&gt;
* nsIDocCharset               [http://lxr.mozilla.org/mozilla/source/intl/chardet/public/nsIDocCharset.idl#41 LXR]&lt;br /&gt;
* nsIContentViewerContainer   [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIContentViewerContainer.idl#43 LXR]&lt;br /&gt;
* nsIInterfaceRequestor       [http://lxr.mozilla.org/mozilla/source/xpcom/base/nsIInterfaceRequestor.idl#42 LXR]&lt;br /&gt;
* nsIScriptGlobalObjectOwner  [http://lxr.mozilla.org/mozilla/source/dom/public/nsIScriptGlobalObjectOwner.h#50 LXR]&lt;br /&gt;
* nsIRefreshURI               [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIRefreshURI.idl#43 LXR]&lt;br /&gt;
* nsIWebProgressListener      [http://lxr.mozilla.org/mozilla/source/uriloader/base/nsIWebProgressListener.idl#47 LXR]&lt;br /&gt;
* nsIEditorDocShell           [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIEditorDocShell.idl#45 LXR]&lt;br /&gt;
* nsIWebPageDescriptor        [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIWebPageDescriptor.idl#38 LXR]&lt;br /&gt;
&lt;br /&gt;
In my view, nsIDocShellTree* and nsIWebShellContainer should all be merged into a single &amp;quot;tree node&amp;quot; interface.  nsIWebShell should merge into nsIDocShell.  nsILinkHandler, not sure.  nsIContentViewerContainer and nsIScriptGlobalObjectOwner, do we really need those?  nsIRefreshURI is probably something to merge into nsIDocShell (or even nsIWebNavigation?).  nsIEditorDocshell also doesn&#039;t really need to be a separate interface.&lt;br /&gt;
&lt;br /&gt;
Then again, do we want to just dump all sorts of stuff onto nsIDocShell?  Not sure about that.  Maybe we should look at who uses nsIDocShell and these other interfaces and why?&lt;br /&gt;
&lt;br /&gt;
== Session history (needs work) ==&lt;br /&gt;
== URI loading (needs work) ==&lt;br /&gt;
== Progress notifications (needs work) ==&lt;br /&gt;
&lt;br /&gt;
== Bugs that could need some Docshell cleanup (needs work) ==&lt;br /&gt;
&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=249751 bug 249751] Links whose onclick closes the window fail to trigger link&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=84833 bug 84833] Calling self.close() right after calling submit() cancels submission&lt;br /&gt;
&lt;br /&gt;
== Current plans for docshell ==&lt;br /&gt;
&lt;br /&gt;
nsWebShell should be merged into nsDocShell&lt;br /&gt;
&lt;br /&gt;
[[DocShell:IRC_Logs]] has some IRC discussions concerning the future direction of docshell and docloader&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Can we eliminate mOSHE/mLSHE in favor of just accessing the shistory&#039;s entry for mIndex/mRequestedIndex?&lt;br /&gt;
&lt;br /&gt;
== Completed Work ==&lt;br /&gt;
&lt;br /&gt;
nsIWebShell removed. Thanks to bz!  -- [http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&amp;amp;module=all&amp;amp;branch=&amp;amp;branchtype=match&amp;amp;dir=&amp;amp;file=&amp;amp;filetype=match&amp;amp;who=&amp;amp;whotype=match&amp;amp;sortby=Date&amp;amp;hours=2&amp;amp;date=explicit&amp;amp;mindate=2005-01-03+14%3A49&amp;amp;maxdate=2005-01-03+14%3A51&amp;amp;cvsroot=%2Fcvsroot Bonsai]&lt;br /&gt;
&lt;br /&gt;
nsDocLoaderImpl ([http://lxr.mozilla.org/mozilla/source/uriloader/base/nsDocLoader.cpp nsDocLoader.cpp]) will be merged into nsDocShell; or rather, nsDocShell will become a subclass of nsDocLoaderImpl (&amp;lt;s&amp;gt;[https://bugzilla.mozilla.org/show_bug.cgi?id=272471 bug 272471]&amp;lt;/s&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
nsIWebShell and nsIWebShellContainer were eliminated (&amp;lt;s&amp;gt;[https://bugzilla.mozilla.org/show_bug.cgi?id=273319 bug 273319]&amp;lt;/s&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;s&amp;gt;[https://bugzilla.mozilla.org/show_bug.cgi?id=261086 bug 261086]&amp;lt;/s&amp;gt; - docshell does not need quite as many things in its GetInterface implementation&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=DocShell&amp;diff=10976</id>
		<title>DocShell</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=DocShell&amp;diff=10976"/>
		<updated>2005-08-13T05:41:15Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Completed Work */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Docshell Documentation =&lt;br /&gt;
&lt;br /&gt;
The goal of this page is to serve as a dumping/organization ground for docshell&lt;br /&gt;
docs.  When someone finds out something, it should be added here in a&lt;br /&gt;
reasonable way.  By the time this gets unwieldy, hopefully we will have enough&lt;br /&gt;
material for several actual docs on what docshell does and why.&lt;br /&gt;
&lt;br /&gt;
Some of these sections need writing, and we may need other sections... Feel free to rearrange as needed&lt;br /&gt;
&lt;br /&gt;
* [http://www.mozilla.org/projects/embedding/docshell.html About] (What actually is docshell?)&lt;br /&gt;
* [[DocShell:Fastback|How fastback is implemented]]&lt;br /&gt;
&lt;br /&gt;
== Interfaces Implemented by Docshell ==&lt;br /&gt;
&lt;br /&gt;
Docshell + webshell implement the following interfaces&lt;br /&gt;
&lt;br /&gt;
Webshell:&lt;br /&gt;
&lt;br /&gt;
* nsIWebShell                 [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShell.h#75 LXR]&lt;br /&gt;
* nsIWebShellContainer        [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShell.h#66 LXR]&lt;br /&gt;
* nsIWebShellServices         [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShellServices.h#52 LXR]&lt;br /&gt;
* nsILinkHandler              [http://lxr.mozilla.org/mozilla/source/webshell/public/nsILinkHandler.h#70 LXR]&lt;br /&gt;
* nsIClipboardCommands (why?) [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIClipboardCommands.idl#42 LXR]&lt;br /&gt;
&lt;br /&gt;
Docshell:&lt;br /&gt;
&lt;br /&gt;
* nsIDocShell                 [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShell.idl#68 LXR]&lt;br /&gt;
* nsIDocShellTreeItem         [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellTreeItem.idl#45 LXR]&lt;br /&gt;
* nsIDocShellTreeNode         [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellTreeNode.idl#44 LXR]&lt;br /&gt;
* nsIDocShellHistory          [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellHistory.idl#42 LXR]&lt;br /&gt;
* nsIWebNavigation            [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIWebNavigation.idl#42 LXR]&lt;br /&gt;
* nsIBaseWindow               [http://lxr.mozilla.org/mozilla/source/widget/public/nsIBaseWindow.idl#51 LXR]&lt;br /&gt;
* nsIScrollable               [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIScrollable.idl#42 LXR]&lt;br /&gt;
* nsITextScroll               [http://lxr.mozilla.org/mozilla/source/docshell/base/nsITextScroll.idl#43 LXR]&lt;br /&gt;
* nsIDocCharset               [http://lxr.mozilla.org/mozilla/source/intl/chardet/public/nsIDocCharset.idl#41 LXR]&lt;br /&gt;
* nsIContentViewerContainer   [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIContentViewerContainer.idl#43 LXR]&lt;br /&gt;
* nsIInterfaceRequestor       [http://lxr.mozilla.org/mozilla/source/xpcom/base/nsIInterfaceRequestor.idl#42 LXR]&lt;br /&gt;
* nsIScriptGlobalObjectOwner  [http://lxr.mozilla.org/mozilla/source/dom/public/nsIScriptGlobalObjectOwner.h#50 LXR]&lt;br /&gt;
* nsIRefreshURI               [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIRefreshURI.idl#43 LXR]&lt;br /&gt;
* nsIWebProgressListener      [http://lxr.mozilla.org/mozilla/source/uriloader/base/nsIWebProgressListener.idl#47 LXR]&lt;br /&gt;
* nsIEditorDocShell           [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIEditorDocShell.idl#45 LXR]&lt;br /&gt;
* nsIWebPageDescriptor        [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIWebPageDescriptor.idl#38 LXR]&lt;br /&gt;
&lt;br /&gt;
In my view, nsIDocShellTree* and nsIWebShellContainer should all be merged into a single &amp;quot;tree node&amp;quot; interface.  nsIWebShell should merge into nsIDocShell.  nsILinkHandler, not sure.  nsIContentViewerContainer and nsIScriptGlobalObjectOwner, do we really need those?  nsIRefreshURI is probably something to merge into nsIDocShell (or even nsIWebNavigation?).  nsIEditorDocshell also doesn&#039;t really need to be a separate interface.&lt;br /&gt;
&lt;br /&gt;
Then again, do we want to just dump all sorts of stuff onto nsIDocShell?  Not sure about that.  Maybe we should look at who uses nsIDocShell and these other interfaces and why?&lt;br /&gt;
&lt;br /&gt;
== Session history (needs work) ==&lt;br /&gt;
== URI loading (needs work) ==&lt;br /&gt;
== Progress notifications (needs work) ==&lt;br /&gt;
&lt;br /&gt;
== Bugs that could need some Docshell cleanup (needs work) ==&lt;br /&gt;
&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=249751 bug 249751] Links whose onclick closes the window fail to trigger link&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=84833 bug 84833] Calling self.close() right after calling submit() cancels submission&lt;br /&gt;
&lt;br /&gt;
== Current plans for docshell ==&lt;br /&gt;
&lt;br /&gt;
nsWebShell should be merged into nsDocShell&lt;br /&gt;
&lt;br /&gt;
[[DocShell:IRC_Logs]] has some IRC discussions concerning the future direction of docshell and docloader&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Can we eliminate mOSHE/mLSHE in favor of just accessing the shistory&#039;s entry for mIndex/mRequestedIndex?&lt;br /&gt;
&lt;br /&gt;
== Completed Work ==&lt;br /&gt;
&lt;br /&gt;
nsIWebShell removed. Thanks to bz!  -- [http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&amp;amp;module=all&amp;amp;branch=&amp;amp;branchtype=match&amp;amp;dir=&amp;amp;file=&amp;amp;filetype=match&amp;amp;who=&amp;amp;whotype=match&amp;amp;sortby=Date&amp;amp;hours=2&amp;amp;date=explicit&amp;amp;mindate=2005-01-03+14%3A49&amp;amp;maxdate=2005-01-03+14%3A51&amp;amp;cvsroot=%2Fcvsroot Bonsai]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
nsDocLoaderImpl ([http://lxr.mozilla.org/mozilla/source/uriloader/base/nsDocLoader.cpp nsDocLoader.cpp]) will be merged into nsDocShell; or rather, nsDocShell will become a subclass of nsDocLoaderImpl ([https://bugzilla.mozilla.org/show_bug.cgi?id=272471 bug 272471])&lt;br /&gt;
&lt;br /&gt;
nsIWebShell and nsIWebShellContainer were eliminated (&amp;lt;s&amp;gt;[https://bugzilla.mozilla.org/show_bug.cgi?id=273319 bug 273319]&amp;lt;/s&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;s&amp;gt;[https://bugzilla.mozilla.org/show_bug.cgi?id=261086 bug 261086]&amp;lt;/s&amp;gt; - docshell does not need quite as many things in its GetInterface implementation&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=DocShell&amp;diff=10975</id>
		<title>DocShell</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=DocShell&amp;diff=10975"/>
		<updated>2005-08-13T05:41:01Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Current plans for docshell */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Docshell Documentation =&lt;br /&gt;
&lt;br /&gt;
The goal of this page is to serve as a dumping/organization ground for docshell&lt;br /&gt;
docs.  When someone finds out something, it should be added here in a&lt;br /&gt;
reasonable way.  By the time this gets unwieldy, hopefully we will have enough&lt;br /&gt;
material for several actual docs on what docshell does and why.&lt;br /&gt;
&lt;br /&gt;
Some of these sections need writing, and we may need other sections... Feel free to rearrange as needed&lt;br /&gt;
&lt;br /&gt;
* [http://www.mozilla.org/projects/embedding/docshell.html About] (What actually is docshell?)&lt;br /&gt;
* [[DocShell:Fastback|How fastback is implemented]]&lt;br /&gt;
&lt;br /&gt;
== Interfaces Implemented by Docshell ==&lt;br /&gt;
&lt;br /&gt;
Docshell + webshell implement the following interfaces&lt;br /&gt;
&lt;br /&gt;
Webshell:&lt;br /&gt;
&lt;br /&gt;
* nsIWebShell                 [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShell.h#75 LXR]&lt;br /&gt;
* nsIWebShellContainer        [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShell.h#66 LXR]&lt;br /&gt;
* nsIWebShellServices         [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShellServices.h#52 LXR]&lt;br /&gt;
* nsILinkHandler              [http://lxr.mozilla.org/mozilla/source/webshell/public/nsILinkHandler.h#70 LXR]&lt;br /&gt;
* nsIClipboardCommands (why?) [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIClipboardCommands.idl#42 LXR]&lt;br /&gt;
&lt;br /&gt;
Docshell:&lt;br /&gt;
&lt;br /&gt;
* nsIDocShell                 [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShell.idl#68 LXR]&lt;br /&gt;
* nsIDocShellTreeItem         [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellTreeItem.idl#45 LXR]&lt;br /&gt;
* nsIDocShellTreeNode         [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellTreeNode.idl#44 LXR]&lt;br /&gt;
* nsIDocShellHistory          [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellHistory.idl#42 LXR]&lt;br /&gt;
* nsIWebNavigation            [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIWebNavigation.idl#42 LXR]&lt;br /&gt;
* nsIBaseWindow               [http://lxr.mozilla.org/mozilla/source/widget/public/nsIBaseWindow.idl#51 LXR]&lt;br /&gt;
* nsIScrollable               [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIScrollable.idl#42 LXR]&lt;br /&gt;
* nsITextScroll               [http://lxr.mozilla.org/mozilla/source/docshell/base/nsITextScroll.idl#43 LXR]&lt;br /&gt;
* nsIDocCharset               [http://lxr.mozilla.org/mozilla/source/intl/chardet/public/nsIDocCharset.idl#41 LXR]&lt;br /&gt;
* nsIContentViewerContainer   [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIContentViewerContainer.idl#43 LXR]&lt;br /&gt;
* nsIInterfaceRequestor       [http://lxr.mozilla.org/mozilla/source/xpcom/base/nsIInterfaceRequestor.idl#42 LXR]&lt;br /&gt;
* nsIScriptGlobalObjectOwner  [http://lxr.mozilla.org/mozilla/source/dom/public/nsIScriptGlobalObjectOwner.h#50 LXR]&lt;br /&gt;
* nsIRefreshURI               [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIRefreshURI.idl#43 LXR]&lt;br /&gt;
* nsIWebProgressListener      [http://lxr.mozilla.org/mozilla/source/uriloader/base/nsIWebProgressListener.idl#47 LXR]&lt;br /&gt;
* nsIEditorDocShell           [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIEditorDocShell.idl#45 LXR]&lt;br /&gt;
* nsIWebPageDescriptor        [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIWebPageDescriptor.idl#38 LXR]&lt;br /&gt;
&lt;br /&gt;
In my view, nsIDocShellTree* and nsIWebShellContainer should all be merged into a single &amp;quot;tree node&amp;quot; interface.  nsIWebShell should merge into nsIDocShell.  nsILinkHandler, not sure.  nsIContentViewerContainer and nsIScriptGlobalObjectOwner, do we really need those?  nsIRefreshURI is probably something to merge into nsIDocShell (or even nsIWebNavigation?).  nsIEditorDocshell also doesn&#039;t really need to be a separate interface.&lt;br /&gt;
&lt;br /&gt;
Then again, do we want to just dump all sorts of stuff onto nsIDocShell?  Not sure about that.  Maybe we should look at who uses nsIDocShell and these other interfaces and why?&lt;br /&gt;
&lt;br /&gt;
== Session history (needs work) ==&lt;br /&gt;
== URI loading (needs work) ==&lt;br /&gt;
== Progress notifications (needs work) ==&lt;br /&gt;
&lt;br /&gt;
== Bugs that could need some Docshell cleanup (needs work) ==&lt;br /&gt;
&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=249751 bug 249751] Links whose onclick closes the window fail to trigger link&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=84833 bug 84833] Calling self.close() right after calling submit() cancels submission&lt;br /&gt;
&lt;br /&gt;
== Current plans for docshell ==&lt;br /&gt;
&lt;br /&gt;
nsWebShell should be merged into nsDocShell&lt;br /&gt;
&lt;br /&gt;
[[DocShell:IRC_Logs]] has some IRC discussions concerning the future direction of docshell and docloader&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Can we eliminate mOSHE/mLSHE in favor of just accessing the shistory&#039;s entry for mIndex/mRequestedIndex?&lt;br /&gt;
&lt;br /&gt;
== Completed Work ==&lt;br /&gt;
&lt;br /&gt;
nsIWebShell removed. Thanks to bz!  -- [http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&amp;amp;module=all&amp;amp;branch=&amp;amp;branchtype=match&amp;amp;dir=&amp;amp;file=&amp;amp;filetype=match&amp;amp;who=&amp;amp;whotype=match&amp;amp;sortby=Date&amp;amp;hours=2&amp;amp;date=explicit&amp;amp;mindate=2005-01-03+14%3A49&amp;amp;maxdate=2005-01-03+14%3A51&amp;amp;cvsroot=%2Fcvsroot Bonsai]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
nsDocLoaderImpl ([http://lxr.mozilla.org/mozilla/source/uriloader/base/nsDocLoader.cpp nsDocLoader.cpp]) will be merged into nsDocShell; or rather, nsDocShell will become a subclass of nsDocLoaderImpl ([https://bugzilla.mozilla.org/show_bug.cgi?id=272471 bug 272471])&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=DocShell&amp;diff=10974</id>
		<title>DocShell</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=DocShell&amp;diff=10974"/>
		<updated>2005-08-13T05:40:12Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Current plans for docshell */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Docshell Documentation =&lt;br /&gt;
&lt;br /&gt;
The goal of this page is to serve as a dumping/organization ground for docshell&lt;br /&gt;
docs.  When someone finds out something, it should be added here in a&lt;br /&gt;
reasonable way.  By the time this gets unwieldy, hopefully we will have enough&lt;br /&gt;
material for several actual docs on what docshell does and why.&lt;br /&gt;
&lt;br /&gt;
Some of these sections need writing, and we may need other sections... Feel free to rearrange as needed&lt;br /&gt;
&lt;br /&gt;
* [http://www.mozilla.org/projects/embedding/docshell.html About] (What actually is docshell?)&lt;br /&gt;
* [[DocShell:Fastback|How fastback is implemented]]&lt;br /&gt;
&lt;br /&gt;
== Interfaces Implemented by Docshell ==&lt;br /&gt;
&lt;br /&gt;
Docshell + webshell implement the following interfaces&lt;br /&gt;
&lt;br /&gt;
Webshell:&lt;br /&gt;
&lt;br /&gt;
* nsIWebShell                 [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShell.h#75 LXR]&lt;br /&gt;
* nsIWebShellContainer        [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShell.h#66 LXR]&lt;br /&gt;
* nsIWebShellServices         [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShellServices.h#52 LXR]&lt;br /&gt;
* nsILinkHandler              [http://lxr.mozilla.org/mozilla/source/webshell/public/nsILinkHandler.h#70 LXR]&lt;br /&gt;
* nsIClipboardCommands (why?) [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIClipboardCommands.idl#42 LXR]&lt;br /&gt;
&lt;br /&gt;
Docshell:&lt;br /&gt;
&lt;br /&gt;
* nsIDocShell                 [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShell.idl#68 LXR]&lt;br /&gt;
* nsIDocShellTreeItem         [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellTreeItem.idl#45 LXR]&lt;br /&gt;
* nsIDocShellTreeNode         [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellTreeNode.idl#44 LXR]&lt;br /&gt;
* nsIDocShellHistory          [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellHistory.idl#42 LXR]&lt;br /&gt;
* nsIWebNavigation            [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIWebNavigation.idl#42 LXR]&lt;br /&gt;
* nsIBaseWindow               [http://lxr.mozilla.org/mozilla/source/widget/public/nsIBaseWindow.idl#51 LXR]&lt;br /&gt;
* nsIScrollable               [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIScrollable.idl#42 LXR]&lt;br /&gt;
* nsITextScroll               [http://lxr.mozilla.org/mozilla/source/docshell/base/nsITextScroll.idl#43 LXR]&lt;br /&gt;
* nsIDocCharset               [http://lxr.mozilla.org/mozilla/source/intl/chardet/public/nsIDocCharset.idl#41 LXR]&lt;br /&gt;
* nsIContentViewerContainer   [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIContentViewerContainer.idl#43 LXR]&lt;br /&gt;
* nsIInterfaceRequestor       [http://lxr.mozilla.org/mozilla/source/xpcom/base/nsIInterfaceRequestor.idl#42 LXR]&lt;br /&gt;
* nsIScriptGlobalObjectOwner  [http://lxr.mozilla.org/mozilla/source/dom/public/nsIScriptGlobalObjectOwner.h#50 LXR]&lt;br /&gt;
* nsIRefreshURI               [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIRefreshURI.idl#43 LXR]&lt;br /&gt;
* nsIWebProgressListener      [http://lxr.mozilla.org/mozilla/source/uriloader/base/nsIWebProgressListener.idl#47 LXR]&lt;br /&gt;
* nsIEditorDocShell           [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIEditorDocShell.idl#45 LXR]&lt;br /&gt;
* nsIWebPageDescriptor        [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIWebPageDescriptor.idl#38 LXR]&lt;br /&gt;
&lt;br /&gt;
In my view, nsIDocShellTree* and nsIWebShellContainer should all be merged into a single &amp;quot;tree node&amp;quot; interface.  nsIWebShell should merge into nsIDocShell.  nsILinkHandler, not sure.  nsIContentViewerContainer and nsIScriptGlobalObjectOwner, do we really need those?  nsIRefreshURI is probably something to merge into nsIDocShell (or even nsIWebNavigation?).  nsIEditorDocshell also doesn&#039;t really need to be a separate interface.&lt;br /&gt;
&lt;br /&gt;
Then again, do we want to just dump all sorts of stuff onto nsIDocShell?  Not sure about that.  Maybe we should look at who uses nsIDocShell and these other interfaces and why?&lt;br /&gt;
&lt;br /&gt;
== Session history (needs work) ==&lt;br /&gt;
== URI loading (needs work) ==&lt;br /&gt;
== Progress notifications (needs work) ==&lt;br /&gt;
&lt;br /&gt;
== Bugs that could need some Docshell cleanup (needs work) ==&lt;br /&gt;
&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=249751 bug 249751] Links whose onclick closes the window fail to trigger link&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=84833 bug 84833] Calling self.close() right after calling submit() cancels submission&lt;br /&gt;
&lt;br /&gt;
== Current plans for docshell ==&lt;br /&gt;
&lt;br /&gt;
nsIWebShell and nsIWebShellContainer were eliminated (&amp;lt;s&amp;gt;[https://bugzilla.mozilla.org/show_bug.cgi?id=273319 bug 273319]&amp;lt;/s&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
nsWebShell should be merged into nsDocShell&lt;br /&gt;
&lt;br /&gt;
&amp;lt;s&amp;gt;[https://bugzilla.mozilla.org/show_bug.cgi?id=261086 bug 261086]&amp;lt;/s&amp;gt; - docshell does not need quite as many things in its GetInterface implementation&lt;br /&gt;
&lt;br /&gt;
[[DocShell:IRC_Logs]] has some IRC discussions concerning the future direction of docshell and docloader&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Can we eliminate mOSHE/mLSHE in favor of just accessing the shistory&#039;s entry for mIndex/mRequestedIndex?&lt;br /&gt;
&lt;br /&gt;
== Completed Work ==&lt;br /&gt;
&lt;br /&gt;
nsIWebShell removed. Thanks to bz!  -- [http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&amp;amp;module=all&amp;amp;branch=&amp;amp;branchtype=match&amp;amp;dir=&amp;amp;file=&amp;amp;filetype=match&amp;amp;who=&amp;amp;whotype=match&amp;amp;sortby=Date&amp;amp;hours=2&amp;amp;date=explicit&amp;amp;mindate=2005-01-03+14%3A49&amp;amp;maxdate=2005-01-03+14%3A51&amp;amp;cvsroot=%2Fcvsroot Bonsai]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
nsDocLoaderImpl ([http://lxr.mozilla.org/mozilla/source/uriloader/base/nsDocLoader.cpp nsDocLoader.cpp]) will be merged into nsDocShell; or rather, nsDocShell will become a subclass of nsDocLoaderImpl ([https://bugzilla.mozilla.org/show_bug.cgi?id=272471 bug 272471])&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=DocShell&amp;diff=10973</id>
		<title>DocShell</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=DocShell&amp;diff=10973"/>
		<updated>2005-08-13T05:38:52Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Current plans for docshell */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Docshell Documentation =&lt;br /&gt;
&lt;br /&gt;
The goal of this page is to serve as a dumping/organization ground for docshell&lt;br /&gt;
docs.  When someone finds out something, it should be added here in a&lt;br /&gt;
reasonable way.  By the time this gets unwieldy, hopefully we will have enough&lt;br /&gt;
material for several actual docs on what docshell does and why.&lt;br /&gt;
&lt;br /&gt;
Some of these sections need writing, and we may need other sections... Feel free to rearrange as needed&lt;br /&gt;
&lt;br /&gt;
* [http://www.mozilla.org/projects/embedding/docshell.html About] (What actually is docshell?)&lt;br /&gt;
* [[DocShell:Fastback|How fastback is implemented]]&lt;br /&gt;
&lt;br /&gt;
== Interfaces Implemented by Docshell ==&lt;br /&gt;
&lt;br /&gt;
Docshell + webshell implement the following interfaces&lt;br /&gt;
&lt;br /&gt;
Webshell:&lt;br /&gt;
&lt;br /&gt;
* nsIWebShell                 [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShell.h#75 LXR]&lt;br /&gt;
* nsIWebShellContainer        [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShell.h#66 LXR]&lt;br /&gt;
* nsIWebShellServices         [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIWebShellServices.h#52 LXR]&lt;br /&gt;
* nsILinkHandler              [http://lxr.mozilla.org/mozilla/source/webshell/public/nsILinkHandler.h#70 LXR]&lt;br /&gt;
* nsIClipboardCommands (why?) [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIClipboardCommands.idl#42 LXR]&lt;br /&gt;
&lt;br /&gt;
Docshell:&lt;br /&gt;
&lt;br /&gt;
* nsIDocShell                 [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShell.idl#68 LXR]&lt;br /&gt;
* nsIDocShellTreeItem         [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellTreeItem.idl#45 LXR]&lt;br /&gt;
* nsIDocShellTreeNode         [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellTreeNode.idl#44 LXR]&lt;br /&gt;
* nsIDocShellHistory          [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIDocShellHistory.idl#42 LXR]&lt;br /&gt;
* nsIWebNavigation            [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIWebNavigation.idl#42 LXR]&lt;br /&gt;
* nsIBaseWindow               [http://lxr.mozilla.org/mozilla/source/widget/public/nsIBaseWindow.idl#51 LXR]&lt;br /&gt;
* nsIScrollable               [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIScrollable.idl#42 LXR]&lt;br /&gt;
* nsITextScroll               [http://lxr.mozilla.org/mozilla/source/docshell/base/nsITextScroll.idl#43 LXR]&lt;br /&gt;
* nsIDocCharset               [http://lxr.mozilla.org/mozilla/source/intl/chardet/public/nsIDocCharset.idl#41 LXR]&lt;br /&gt;
* nsIContentViewerContainer   [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIContentViewerContainer.idl#43 LXR]&lt;br /&gt;
* nsIInterfaceRequestor       [http://lxr.mozilla.org/mozilla/source/xpcom/base/nsIInterfaceRequestor.idl#42 LXR]&lt;br /&gt;
* nsIScriptGlobalObjectOwner  [http://lxr.mozilla.org/mozilla/source/dom/public/nsIScriptGlobalObjectOwner.h#50 LXR]&lt;br /&gt;
* nsIRefreshURI               [http://lxr.mozilla.org/mozilla/source/webshell/public/nsIRefreshURI.idl#43 LXR]&lt;br /&gt;
* nsIWebProgressListener      [http://lxr.mozilla.org/mozilla/source/uriloader/base/nsIWebProgressListener.idl#47 LXR]&lt;br /&gt;
* nsIEditorDocShell           [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIEditorDocShell.idl#45 LXR]&lt;br /&gt;
* nsIWebPageDescriptor        [http://lxr.mozilla.org/mozilla/source/docshell/base/nsIWebPageDescriptor.idl#38 LXR]&lt;br /&gt;
&lt;br /&gt;
In my view, nsIDocShellTree* and nsIWebShellContainer should all be merged into a single &amp;quot;tree node&amp;quot; interface.  nsIWebShell should merge into nsIDocShell.  nsILinkHandler, not sure.  nsIContentViewerContainer and nsIScriptGlobalObjectOwner, do we really need those?  nsIRefreshURI is probably something to merge into nsIDocShell (or even nsIWebNavigation?).  nsIEditorDocshell also doesn&#039;t really need to be a separate interface.&lt;br /&gt;
&lt;br /&gt;
Then again, do we want to just dump all sorts of stuff onto nsIDocShell?  Not sure about that.  Maybe we should look at who uses nsIDocShell and these other interfaces and why?&lt;br /&gt;
&lt;br /&gt;
== Session history (needs work) ==&lt;br /&gt;
== URI loading (needs work) ==&lt;br /&gt;
== Progress notifications (needs work) ==&lt;br /&gt;
&lt;br /&gt;
== Bugs that could need some Docshell cleanup (needs work) ==&lt;br /&gt;
&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=249751 bug 249751] Links whose onclick closes the window fail to trigger link&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=84833 bug 84833] Calling self.close() right after calling submit() cancels submission&lt;br /&gt;
&lt;br /&gt;
== Current plans for docshell ==&lt;br /&gt;
&lt;br /&gt;
nsIWebShell and nsIWebShellContainer were eliminated ([https://bugzilla.mozilla.org/show_bug.cgi?id=273319 bug 273319])&lt;br /&gt;
&lt;br /&gt;
nsWebShell should be merged into nsDocShell&lt;br /&gt;
&lt;br /&gt;
[https://bugzilla.mozilla.org/show_bug.cgi?id=261086 bug 261086] - docshell does not need quite as many things in its GetInterface implementation&lt;br /&gt;
&lt;br /&gt;
[[DocShell:IRC_Logs]] has some IRC discussions concerning the future direction of docshell and docloader&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Can we eliminate mOSHE/mLSHE in favor of just accessing the shistory&#039;s entry for mIndex/mRequestedIndex?&lt;br /&gt;
&lt;br /&gt;
== Completed Work ==&lt;br /&gt;
&lt;br /&gt;
nsIWebShell removed. Thanks to bz!  -- [http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&amp;amp;module=all&amp;amp;branch=&amp;amp;branchtype=match&amp;amp;dir=&amp;amp;file=&amp;amp;filetype=match&amp;amp;who=&amp;amp;whotype=match&amp;amp;sortby=Date&amp;amp;hours=2&amp;amp;date=explicit&amp;amp;mindate=2005-01-03+14%3A49&amp;amp;maxdate=2005-01-03+14%3A51&amp;amp;cvsroot=%2Fcvsroot Bonsai]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
nsDocLoaderImpl ([http://lxr.mozilla.org/mozilla/source/uriloader/base/nsDocLoader.cpp nsDocLoader.cpp]) will be merged into nsDocShell; or rather, nsDocShell will become a subclass of nsDocLoaderImpl ([https://bugzilla.mozilla.org/show_bug.cgi?id=272471 bug 272471])&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Firefox:1.5_Network_Error_Messages&amp;diff=10674</id>
		<title>Firefox:1.5 Network Error Messages</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Firefox:1.5_Network_Error_Messages&amp;diff=10674"/>
		<updated>2005-07-29T04:49:54Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Error message text for netError.dtd */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Error message text for netError.dtd=&lt;br /&gt;
Firefox 1.5 will feature user-friendly error messages to help users when they encounter various network errors that result in pages not loading. Due to some overlap and checkin depedencies between the rendering of the error messages ([https://bugzilla.mozilla.org/show_bug.cgi?id=280190 bug 280190]), and the error message text ([https://bugzilla.mozilla.org/show_bug.cgi?id=301208 bug 301208]) this wiki is being used to synchronize the error text changes until it&#039;s time to patch the file itself.&lt;br /&gt;
&lt;br /&gt;
You can see a preview of the error message rendering [http://hskupin.info/tmp/netError/v13/ltr-fx.jpg here].&lt;br /&gt;
&lt;br /&gt;
The latest proposed patch to the netError.dtd file is [http://lxr.mozilla.org/seamonkey/source/dom/locales/en-US/chrome/netError.dtd here].&lt;br /&gt;
&lt;br /&gt;
== Open Issues &amp;amp; Questions ==&lt;br /&gt;
* &amp;lt;strike&amp;gt;will we have access to the attempted URL for use in the error messages?&amp;lt;/strike&amp;gt;&lt;br /&gt;
** Yes, the URL is available.&lt;br /&gt;
** ok, using %address to refer to the attempted URI. --[[User:Beltzner|Beltzner]] 14:26, 27 Jul 2005 (PDT)&lt;br /&gt;
* will we have access to the product name for use in the error messages?&lt;br /&gt;
** Not yet, but we will have ([https://bugzilla.mozilla.org/show_bug.cgi?id=302309  bug 302309])&lt;br /&gt;
** ok for now will assume &amp;quot;Firefox&amp;quot; will resolve to some environment variable that&#039;s accessable from these messaages --[[User:Beltzner|Beltzner]] 14:26, 27 Jul 2005 (PDT)&lt;br /&gt;
* not sure about [[Firefox:1.5_Network_Error_Messages#redirectLoop|redirectLoop&#039;s]] recommendation to turn on cookies; security/privacy issues?&lt;br /&gt;
** That does seem to be the correct solution the redirectLoop problem in my experience, security/privacy issues aside.  ([http://weather.com weather.com] is/was a particularly bad offender, as blocking cookies from one of its subdomains would cause the infinite redirect loop.) --[[User:Sardisson|Sardisson]] 20:35, 28 Jul 2005 (PDT)&lt;br /&gt;
* not sure about [[Firefox:1.5_Network_Error_Messages#deniedPortAccess|deniedPortAccess&#039;s]] recommendation about plugins/3rd party apps; could that happen?&lt;br /&gt;
** I don&#039;t think so; plugins should affect protocols, not port security when browsing HTTP.  Could be wrong. --[[User:Wrprice|Wrprice]] 12:27, 28 Jul 2005 (PDT)&lt;br /&gt;
* Should some distinction be made for firewall/proxy possibilities between the browser&#039;s settings vs. the proxy/firewall&#039;s settings?  (somewhat critical distinction)&lt;br /&gt;
** Proxy allows Firefox, but Firefox not set to use proxy.&lt;br /&gt;
** Firefox set to use proxy, but proxy/firewall does not allow the browser?&lt;br /&gt;
* Can&#039;t reference &amp;quot;Preferences&amp;quot; as an absolute because on Windows builds it&#039;s &amp;quot;Tools&amp;quot; &amp;gt; &amp;quot;Options&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
== Error Page label &amp;amp; retry button label ==&lt;br /&gt;
* loadError.label = &amp;quot;Problem loading page&amp;quot;&lt;br /&gt;
* retry.label = &amp;quot;Try again&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== connectionFailure ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;Can&#039;t connect to this address&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox can&#039;t establish a connection to the server at %address.&lt;br /&gt;
*The site could be temporarily unavailable or too busy. Try again in a few moments.&lt;br /&gt;
*If you are unable to load any addresses, check the computer&#039;s network connection.&lt;br /&gt;
*If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.&lt;br /&gt;
&lt;br /&gt;
== deniedPortAccess ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;This port is restricted&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
This address (%address) specifies a network port which is normally used for purposes other than Web browsing. Firefox has canceled the request for your protection.&lt;br /&gt;
*You might need to install a plugin or other software to view this address. Go back to the previous page and check the site for any special requirements.&lt;br /&gt;
&lt;br /&gt;
== dnsNotFound ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;Can&#039;t find this server&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox can&#039;t find the server at %address.&lt;br /&gt;
*Check the address for typing errors such as &amp;lt;b&amp;gt;ww&amp;lt;/b&amp;gt;.mozilla.org instead of &amp;lt;b&amp;gt;www&amp;lt;/b&amp;gt;.mozilla.org&lt;br /&gt;
*If you are unable to load any addresses, check the computer&#039;s network connection.&lt;br /&gt;
*If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.&lt;br /&gt;
&lt;br /&gt;
== fileNotFound ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;Can&#039;t load this file&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox can&#039;t find the file at %address.&lt;br /&gt;
*Check the file name for for capitalization or other typing errors.&lt;br /&gt;
*Be sure that you have the required access to see the file at this address.&lt;br /&gt;
*Check to see if the file was moved, renamed or deleted.&lt;br /&gt;
&lt;br /&gt;
== generic ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;Can&#039;t complete the request&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox has experienced a problem, and can&#039;t complete the current request right now.&lt;br /&gt;
&lt;br /&gt;
== malformedURI ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;The address isn&#039;t valid&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
%address isn&#039;t in a recognized format.&lt;br /&gt;
*Web addresses are usually written like &amp;lt;b&amp;gt;http://www.example.com&amp;lt;/b&amp;gt;&lt;br /&gt;
*Make sure that you&#039;re using forward slashes (i.e. &amp;lt;b&amp;gt;/&amp;lt;/b&amp;gt;).&lt;br /&gt;
&lt;br /&gt;
shouldn&#039;t that be i.e. instead of e.g.? --[[User:Biesi|Biesi]] 06:34, 27 Jul 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
yeah, I think you&#039;re right; but maybe we don&#039;t need to use either? &amp;quot;..backwards slashes (\)? Addresses need to use forward slashes (/)&amp;quot;? --[[User:Beltzner|Beltzner]] 07:52, 27 Jul 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== netInterrupt ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;The connection was interrupted&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt; &amp;lt;br&amp;gt;&lt;br /&gt;
The connection to the server at %address was interrupted while the page was loading.&lt;br /&gt;
*The site could be temporarily unavailable or too busy. Try again in a few moments.&lt;br /&gt;
*If you are unable to load any addresses, check the computer&#039;s network connection.&lt;br /&gt;
*If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.&lt;br /&gt;
&lt;br /&gt;
== netOffline ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;Offline mode&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox is currently in &amp;quot;offline mode&amp;quot; and is unable to browse the Web.&lt;br /&gt;
*Uncheck &amp;quot;Work Offline&amp;quot; in the &amp;quot;File&amp;quot; menu to take the browser out of offline mode.&lt;br /&gt;
&lt;br /&gt;
== netReset ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;The connection was reset&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
The connection to the server at %address was reset while the page was loading.&lt;br /&gt;
*The site could be temporarily unavailable or too busy. Try again in a few moments.&lt;br /&gt;
*If you are unable to load any addresses, check the computer&#039;s network connection.&lt;br /&gt;
*If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.&lt;br /&gt;
&lt;br /&gt;
== netTimeout ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;The connection timed out&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox got tired of waiting to hear back from the server at %address.&lt;br /&gt;
*The site could be temporarily unavailable or too busy. Try again in a few moments.&lt;br /&gt;
*If you are unable to load any addresses, check the computer&#039;s network connection.&lt;br /&gt;
*If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.&lt;br /&gt;
&lt;br /&gt;
== protocolNotFound ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;That protocol isn&#039;t recognized&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox isn&#039;t sure what protocol is being specified by %address.&lt;br /&gt;
*You might need to install a plugin or other software to view this address. Go back to the previous page and check the site for any special requirements.&lt;br /&gt;
&lt;br /&gt;
== proxyConnectFailure ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;The proxy server is refusing connections&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox is configured to use a proxy server, but that proxy server is refusing connections.&lt;br /&gt;
*Check the proxy settings in &amp;quot;Preferences&amp;quot; to make sure they are correct.&lt;br /&gt;
&lt;br /&gt;
== proxyResolveFailure ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;The proxy server can&#039;t be found&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox is configured to use a proxy server, but that proxy server cannot be found.&lt;br /&gt;
*Check the proxy settings in &amp;quot;Preferences&amp;quot; to make sure they are correct.&lt;br /&gt;
*Check to make sure you computer has a working network connection.&lt;br /&gt;
*If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.&lt;br /&gt;
&lt;br /&gt;
== redirectLoop ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;The page isn&#039;t redirecting properly&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox has detected that the server is redirecting the request for %address in a way that will never complete.&lt;br /&gt;
*Change your cookies settings in &amp;quot;Preferences&amp;quot; to accept cookies for this site.&lt;br /&gt;
&lt;br /&gt;
== unknownSocketType ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;Unexpected response from server&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
The server at %address responded to the request in an unexpected way, and Firefox cannot continue.&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Firefox:1.5_Network_Error_Messages&amp;diff=10553</id>
		<title>Firefox:1.5 Network Error Messages</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Firefox:1.5_Network_Error_Messages&amp;diff=10553"/>
		<updated>2005-07-27T07:02:39Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Error message text for netError.dtd */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Error message text for netError.dtd=&lt;br /&gt;
Firefox 1.5 will feature user-friendly error messages to help users when they encounter various network errors that result in pages not loading. Due to some overlap and checkin depedencies between the rendering of the error messages ([https://bugzilla.mozilla.org/show_bug.cgi?id=280190 bug 280190]), and the error message text ([https://bugzilla.mozilla.org/show_bug.cgi?id=301208 bug 301208]) this wiki is being used to synchronize the error text changes until it&#039;s time to patch the file itself.&lt;br /&gt;
&lt;br /&gt;
You can see a preview of the error message rendering [http://hskupin.info/tmp/netError/v13/ltr-fx.jpg here].&lt;br /&gt;
&lt;br /&gt;
The latest proposed patch to the netError.dtd file is [https://bugzilla.mozilla.org/attachment.cgi?id=190672 here].&lt;br /&gt;
&lt;br /&gt;
== Questions ==&lt;br /&gt;
* will we have access to the attempted URL for use in the error messages?&lt;br /&gt;
* will we have access to the product name for use in the error messages?&lt;br /&gt;
&lt;br /&gt;
== Error Page label &amp;amp; retry button label ==&lt;br /&gt;
* loadError.label = &amp;quot;Problem loading page&amp;quot;&lt;br /&gt;
* retry.label = &amp;quot;Try again&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== connectionFailure ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;Can&#039;t connect to this address&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox can&#039;t establish a connection to the server at this address.&lt;br /&gt;
*Could the site be temporarily unavailable? Click &amp;quot;Try Again&amp;quot;.&lt;br /&gt;
*Are you unable to connect to other sites?  Check the computer&#039;s network connection.&lt;br /&gt;
*Is your computer or network protected by a firewall or proxy? Make sure that Firefox is permitted to access the web.&lt;br /&gt;
&lt;br /&gt;
== deniedPortAccess ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;This port is restricted&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
This address specifies a network port which is normally used for purposes [em]other[/em] than web browsing. Firefox has canceled the request for your protection.&lt;br /&gt;
*Were you trying to view a multimedia or other special type of file? You might need to install a plugin or other software to view the file properly. Use the &amp;quot;Back&amp;quot; button on your browser and check the site for any special requirements.&lt;br /&gt;
*Are you lost? Click the &amp;quot;Back&amp;quot; button to go back to the previous page.&lt;br /&gt;
&lt;br /&gt;
== dnsNotFound ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;Can&#039;t find this server&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox can&#039;t find the server at this address.&lt;br /&gt;
*Is there a mistake in the address? Check for typing errors such as &amp;lt;b&amp;gt;ww&amp;lt;/b&amp;gt;.mozilla.org instead of &amp;lt;b&amp;gt;www&amp;lt;/b&amp;gt;.mozilla.org&lt;br /&gt;
*Are you unable to find other sites? Check the computer&#039;s network connection.&lt;br /&gt;
*Is your computer or network protected by a firewall or proxy? Make sure that Firefox is permitted to access the web.&lt;br /&gt;
&lt;br /&gt;
== fileNotFound ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;Can&#039;t load this file&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox can&#039;t find the file at this address.&lt;br /&gt;
*Is there a mistake in the address? Check for capitalization or other typing errors.&lt;br /&gt;
*Could the file have been moved, renamed or deleted?&lt;br /&gt;
*Do you have the required access to see the file at this address?&lt;br /&gt;
&lt;br /&gt;
== generic ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;Can&#039;t complete the request&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox has experienced a problem, and can&#039;t complete the current request right now.&lt;br /&gt;
&lt;br /&gt;
== malformedURI ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;The address isn&#039;t valid&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
This address isn&#039;t in a recognized format.&lt;br /&gt;
*Does it start with &amp;lt;b&amp;gt;http://&amp;lt;/b&amp;gt;? Typical address are of the form &amp;lt;b&amp;gt;http://www.somewhere.com&amp;lt;/b&amp;gt;&lt;br /&gt;
*Does it contain backwards slashes (e.g. &amp;lt;b&amp;gt;\&amp;lt;/b&amp;gt;)? Addresses need to use forward slashes (e.g. &amp;lt;b&amp;gt;/&amp;lt;/b&amp;gt;).&lt;br /&gt;
*Is there an extra space? Addresses cannot have empty spaces in the middle.&lt;br /&gt;
&lt;br /&gt;
== netInterrupt ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;The connection was interrupted&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt; &amp;lt;br&amp;gt;&lt;br /&gt;
The connection to the server at this address was interrupted while the page was loading.&lt;br /&gt;
*Could the site be temporarily unavailable? Click &amp;quot;Try Again&amp;quot;.&lt;br /&gt;
*Are you unable to connect to other sites?  Check the computer&#039;s network connection.&lt;br /&gt;
*Is your computer or network protected by a firewall or proxy? Make sure that Firefox is permitted to access the web.&lt;br /&gt;
&lt;br /&gt;
== netOffline ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;Can&#039;t browse in offline mode&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox is currently in &amp;quot;offline mode&amp;quot; and is unable to browse the web.&lt;br /&gt;
*Is your computer on an active network? Use the &amp;quot;File&amp;quot; menu to take the browser out of offline mode and then click &amp;quot;Try Again&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
== netReset ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;The connection was reset&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
The connection to the server at this address was reset while the page was loading.&lt;br /&gt;
*Could the site be temporarily unavailable? Click &amp;quot;Try Again&amp;quot;.&lt;br /&gt;
*Are you unable to connect to other sites?  Check the computer&#039;s network connection.&lt;br /&gt;
*Is your computer or network protected by a firewall or proxy? Make sure that Firefox is permitted to access the web.&lt;br /&gt;
&lt;br /&gt;
== netTimeout ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;The connection timed out&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox got tired of waiting to hear back from the server at this address.&lt;br /&gt;
*Could the site be temporarily unavailable or too busy? Click &amp;quot;Try Again&amp;quot;.&lt;br /&gt;
*Are you unable to connect to other sites?  Check the computer&#039;s network connection.&lt;br /&gt;
*Is your computer or network protected by a firewall or proxy? Make sure that Firefox is permitted to access the web.&lt;br /&gt;
&lt;br /&gt;
== protocolNotFound ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;That protocol isn&#039;t recognized&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox isn&#039;t sure what protocol is being specified by this address.&lt;br /&gt;
*Were you trying to view a multimedia or other special type of file? You might need to install a plugin or other software to view the file properly. Use the &amp;quot;Back&amp;quot; button on your browser and check the site for any special requirements.&lt;br /&gt;
&lt;br /&gt;
== proxyConnectFailure ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;The proxy server is refusing connections&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox is configured to use a proxy server, but that proxy server is refusing connections.&lt;br /&gt;
*Are the proxy settings correct? Check the settings in &amp;quot;Preferences&amp;quot; and click &amp;quot;Try Again&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
== proxyResolveFailure ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;The proxy server can&#039;t be found&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox is configured to use a proxy server, but that proxy server cannot be found.&lt;br /&gt;
*Are the proxy settings correct? Check the settings in &amp;quot;Preferences&amp;quot; and click &amp;quot;Try Again&amp;quot;.&lt;br /&gt;
*Are you unable to connect to other sites?  Check the computer&#039;s network connection.&lt;br /&gt;
*Is your computer or network protected by a firewall or proxy? Make sure that Firefox is permitted to access the web.&lt;br /&gt;
&lt;br /&gt;
== redirectLoop ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;The page isn&#039;t redirecting properly&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Firefox has detected that the server at this address is redirecting the request in a way that will never complete.&lt;br /&gt;
*Have you disabled or blocked cookies? Change your cookies settings in &amp;quot;Preferences&amp;quot; to accept cookies for this site and click &amp;quot;Try Again&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
== unknownSocketType ==&lt;br /&gt;
&amp;lt;b&amp;gt;&amp;lt;u&amp;gt;Unexpected response from server&amp;lt;/u&amp;gt;&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
The server at this address responded to the request in an unexpected way, and Firefox cannot continue.&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=6660</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=6660"/>
		<updated>2005-04-28T14:27:47Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Intro */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
*No. It&#039;s never a good thing to try and extend HTML, and Netscape&#039;s failure to realize this is one of the reasons for IE&#039;s market share today. You&#039;re right that there&#039;s no use in explaining further since this wouldn&#039;t happen anyway. :-)--[[User:Omikron|Omikron]] 08:54, 26 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
* Every accessibility guide will tell you the same: new windows confuse users, and because Firefox opens new tabs so seemlessly, the user will sometimes wonder why the back button doesn&#039;t work (even I do this sometimes). The only logical behaviour would be to close the recently opened window in order to revert to the previous location. This should be coupled with an Undo Close Tab feature, but will give a significant accessibility advantage to Firefox.--[[User:Omikron|Omikron]] 08:48, 26 Apr 2005 (PDT)&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
** Agreed, Firefox is aimed at Mum &amp;amp; Dad users so I see no reason why the navigation paradigm should be updated to fit modern browsers. Firefox could have the edge by having the &#039;&#039;&#039;easiest&#039;&#039;&#039; navigation of any browser by far. The back button is for going back to the previous page, why oh why does no browser keep the back button enabled on new windows/tabs? (except IE!) because nobody is thinking about Mum &amp;amp; Dad and doesn&#039;t see the difficulty in constantly switching paradigms. I&#039;ve mentioned this idea on Blake&#039;s Blog twice and here in the Wiki and still nobody seems interested! If Firefox ever wants to be the easiest browser of all, it needs to update the back button paradigm!&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; [[User:Kroc|Kroc]] 12:48, 26 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
=== Intro ===&lt;br /&gt;
&lt;br /&gt;
Firefox only offers very basic tabbed browsing functionality, something that should be addressed until 2.0.&lt;br /&gt;
&lt;br /&gt;
As a user who tried out all the latest browsers there are special features I&#039;ve grown to like which should simply be built-in into Firefox.&lt;br /&gt;
Some may argue that you can find an extension for everything, but some novice users simply can&#039;t find those extensions, or even configure them properly.&lt;br /&gt;
&lt;br /&gt;
I will try to form some kind of a proposal for improved tabbed browsing in this section, and once it&#039;s ready I will move this section to [[Firefox:2.0 Tabbed Browsing]]. &lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;: This is still WIP and every now and then I will be adding new things to it.&lt;br /&gt;
&lt;br /&gt;
If you have any comments/suggestions, add them in the [[Talk:Firefox:2.0_Tabbed_Browsing#Users.27_Comments|Comments section]]&lt;br /&gt;
&lt;br /&gt;
=== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ===&lt;br /&gt;
&lt;br /&gt;
Discussed features:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Tabbed Browsing Presets&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Window Modes&#039;&#039;&#039;&lt;br /&gt;
* Tab Behaviour&lt;br /&gt;
** Focus Settings&lt;br /&gt;
* Tab Appearance &lt;br /&gt;
* &#039;&#039;&#039;Tab Groups&#039;&#039;&#039;&lt;br /&gt;
* Tab Sessions&lt;br /&gt;
* Tab History (Last Opened Tabs for the current session)&lt;br /&gt;
* Extensions&lt;br /&gt;
&lt;br /&gt;
=== In Detail ===&lt;br /&gt;
&lt;br /&gt;
==== Tabbed Browsing Presets ====&lt;br /&gt;
A preset is a set of prefs and their values. The preset will only contains prefs that modify the tabbed browsing configuration.&lt;br /&gt;
This will allow us to ship Firefox with preconfigured presets (Legacy Preset and Modern Preset).&lt;br /&gt;
The Legay Preset will be configured to have the same functionality that Firefox 1.0 offered (for those who still prefer it), and the Modern Preset will be configured for the optimal tabbed browsing experience (should be turned on by default).&lt;br /&gt;
&lt;br /&gt;
==== Window Modes ====&lt;br /&gt;
Firefox should support 3 types of window modes:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use Multiple Windows&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this mode any action that is set to open a new window, will do so. Of course, the user can still force to open in a new tab via a middle-click, or any other shortcut he sets for &amp;quot;open in a new tab&amp;quot;.&lt;br /&gt;
This should be a part of the Firefox Legacy Preset.&lt;br /&gt;
: Note: Starting another Firefox process should open a new window pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use Multiple Windows when Forced&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this mode windows will only be opened explicitly (by user request). Any action that should want to open a new window, will open it in a new tab instead, unless the user explicitly wants it in a new window (Example: For links, Right Click -&amp;gt; Open in a new Window).&lt;br /&gt;
: Note: Starting another Firefox process should open a new window pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use a Single Window&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This mode will force any action that opens a new window to open in a new tab. Firefox cannot have multiple instances open (unless it&#039;s a different version of Firefox that&#039;s open).&lt;br /&gt;
&#039;This mode should also disable/remove any menu items that say &amp;quot;Open in a New Window&amp;quot;.&lt;br /&gt;
: Note: Starting another Firefox process should open a new tab pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Tab Grouping ====&lt;br /&gt;
Tab Grouping is a way to identify a group of tabs as one. There might be several uses for this feature, but at the moment it should be the lowest of priorities (unless users vote for it).&lt;br /&gt;
There&#039;s not much to say, except describe the configuration of this feature, so here are the prefs for it:&lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;&#039;Tab Grouping Preferences&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;General&#039;&#039;&#039;:&lt;br /&gt;
* Tab Groups - Enabled/Disabled&lt;br /&gt;
** This simply enabled/disabled the feature altogether.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Group tabs by&#039;&#039;&#039;:&lt;br /&gt;
* Location (All tabs originitating from the same website are grouped)&lt;br /&gt;
* &amp;lt;Need more ideas&amp;gt;&amp;lt;br&amp;gt;&#039;&#039;&#039;Note&#039;&#039;&#039;: that there are things that override this, such as the Open as Tab Group feature in the Bookmarks&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Identify groups by&#039;&#039;&#039;:&lt;br /&gt;
* Number&lt;br /&gt;
* Color&amp;lt;br&amp;gt;This pref simply tells us how to mark each tab that&#039;s part of a group. For example.&amp;lt;br&amp;gt;if Color is chosen, then each group of tabs will have a different color. The colors must be unique and bright (maybe allow them to be themed?).&amp;lt;br&amp;gt;If Number is chosen, then each tab group recieves a special ID (the first one gets &amp;quot;1&amp;quot;, the second &amp;quot;2&amp;quot;, etc..). &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Misc&#039;&#039;&#039;:&lt;br /&gt;
* Only one active group at a time.&lt;br /&gt;
** This feature will reduce the clutter of having many tabs open by collapsing a group of tabs into one when you focus another group.&amp;lt;br&amp;gt;When you select a collapsed group of tabs, the group expands by showing all the tabs in that group (and the previous groups collapses), and the tab that was previously focused will retain its focus.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
When Tab Grouping is enabled, two new items are added to the Bookmarks menus:&lt;br /&gt;
* Open as Tab Group&lt;br /&gt;
* Bookmark Tab Group (similar to the Bookmark tabs in one folder)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;: Any new tab will be opened after the last tab of the currently focused group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Things to consider adding&amp;lt;/u&amp;gt;:&lt;br /&gt;
* Allow custom tab groups, so even that you have a few pages from the same website open, you can have them in different groups.&lt;br /&gt;
&lt;br /&gt;
=== Users&#039; Comments ===&lt;br /&gt;
* Your comments here&lt;br /&gt;
* And here...&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5609</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5609"/>
		<updated>2005-04-25T15:36:40Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Tab Grouping */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
=== Intro ===&lt;br /&gt;
&lt;br /&gt;
Firefox only offers very basic tabbed browsing functionality, something that must be addressed before 2.0 (Of cousre some features can be pushed back to 2.0).&lt;br /&gt;
&lt;br /&gt;
As a user who tried out all the latest browsers there are special features I&#039;ve grown to like which should simply be built-in into Firefox.&lt;br /&gt;
Some may argue that you can find an extension for everything, but some novice users simply can&#039;t find those extensions, or even configure them properly.&lt;br /&gt;
&lt;br /&gt;
I will try to form some kind of a proposal for improved tabbed browsing in this section, and once it&#039;s ready I will move this section to [[Firefox:2.0 Tabbed Browsing]]. &lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;: This is still WIP and every now and then I will be adding new things to it.&lt;br /&gt;
&lt;br /&gt;
If you have any comments/suggestions, add them in the [[Talk:Firefox:2.0_Tabbed_Browsing#Users.27_Comments|Comments section]]&lt;br /&gt;
&lt;br /&gt;
=== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ===&lt;br /&gt;
&lt;br /&gt;
Discussed features:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Tabbed Browsing Presets&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Window Modes&#039;&#039;&#039;&lt;br /&gt;
* Tab Behaviour&lt;br /&gt;
** Focus Settings&lt;br /&gt;
* Tab Appearance &lt;br /&gt;
* &#039;&#039;&#039;Tab Groups&#039;&#039;&#039;&lt;br /&gt;
* Tab Sessions&lt;br /&gt;
* Tab History (Last Opened Tabs for the current session)&lt;br /&gt;
* Extensions&lt;br /&gt;
&lt;br /&gt;
=== In Detail ===&lt;br /&gt;
&lt;br /&gt;
==== Tabbed Browsing Presets ====&lt;br /&gt;
A preset is a set of prefs and their values. The preset will only contains prefs that modify the tabbed browsing configuration.&lt;br /&gt;
This will allow us to ship Firefox with preconfigured presets (Legacy Preset and Modern Preset).&lt;br /&gt;
The Legay Preset will be configured to have the same functionality that Firefox 1.0 offered (for those who still prefer it), and the Modern Preset will be configured for the optimal tabbed browsing experience (should be turned on by default).&lt;br /&gt;
&lt;br /&gt;
==== Window Modes ====&lt;br /&gt;
Firefox should support 3 types of window modes:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use Multiple Windows&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this mode any action that is set to open a new window, will do so. Of course, the user can still force to open in a new tab via a middle-click, or any other shortcut he sets for &amp;quot;open in a new tab&amp;quot;.&lt;br /&gt;
This should be a part of the Firefox Legacy Preset.&lt;br /&gt;
: Note: Starting another Firefox process should open a new window pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use Multiple Windows when Forced&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this mode windows will only be opened explicitly (by user request). Any action that should want to open a new window, will open it in a new tab instead, unless the user explicitly wants it in a new window (Example: For links, Right Click -&amp;gt; Open in a new Window).&lt;br /&gt;
: Note: Starting another Firefox process should open a new window pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use a Single Window&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This mode will force any action that opens a new window to open in a new tab. Firefox cannot have multiple instances open (unless it&#039;s a different version of Firefox that&#039;s open).&lt;br /&gt;
&#039;This mode should also disable/remove any menu items that say &amp;quot;Open in a New Window&amp;quot;.&lt;br /&gt;
: Note: Starting another Firefox process should open a new tab pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Tab Grouping ====&lt;br /&gt;
Tab Grouping is a way to identify a group of tabs as one. There might be several uses for this feature, but at the moment it should be the lowest of priorities (unless users vote for it).&lt;br /&gt;
There&#039;s not much to say, except describe the configuration of this feature, so here are the prefs for it:&lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;&#039;Tab Grouping Preferences&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;General&#039;&#039;&#039;:&lt;br /&gt;
* Tab Groups - Enabled/Disabled&lt;br /&gt;
** This simply enabled/disabled the feature altogether.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Group tabs by&#039;&#039;&#039;:&lt;br /&gt;
* Location (All tabs originitating from the same website are grouped)&lt;br /&gt;
* &amp;lt;Need more ideas&amp;gt;&amp;lt;br&amp;gt;&#039;&#039;&#039;Note&#039;&#039;&#039;: that there are things that override this, such as the Open as Tab Group feature in the Bookmarks&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Identify groups by&#039;&#039;&#039;:&lt;br /&gt;
* Number&lt;br /&gt;
* Color&amp;lt;br&amp;gt;This pref simply tells us how to mark each tab that&#039;s part of a group. For example.&amp;lt;br&amp;gt;if Color is chosen, then each group of tabs will have a different color. The colors must be unique and bright (maybe allow them to be themed?).&amp;lt;br&amp;gt;If Number is chosen, then each tab group recieves a special ID (the first one gets &amp;quot;1&amp;quot;, the second &amp;quot;2&amp;quot;, etc..). &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Misc&#039;&#039;&#039;:&lt;br /&gt;
* Only one active group at a time.&lt;br /&gt;
** This feature will reduce the clutter of having many tabs open by collapsing a group of tabs into one when you focus another group.&amp;lt;br&amp;gt;When you select a collapsed group of tabs, the group expands by showing all the tabs in that group (and the previous groups collapses), and the tab that was previously focused will retain its focus.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
When Tab Grouping is enabled, two new items are added to the Bookmarks menus:&lt;br /&gt;
* Open as Tab Group&lt;br /&gt;
* Bookmark Tab Group (similar to the Bookmark tabs in one folder)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;: Any new tab will be opened after the last tab of the currently focused group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Things to consider adding&amp;lt;/u&amp;gt;:&lt;br /&gt;
* Allow custom tab groups, so even that you have a few pages from the same website open, you can have them in different groups.&lt;br /&gt;
&lt;br /&gt;
=== Users&#039; Comments ===&lt;br /&gt;
* Your comments here&lt;br /&gt;
* And here...&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5592</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5592"/>
		<updated>2005-04-25T15:07:34Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Intro */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
=== Intro ===&lt;br /&gt;
&lt;br /&gt;
Firefox only offers very basic tabbed browsing functionality, something that must be addressed before 2.0 (Of cousre some features can be pushed back to 2.0).&lt;br /&gt;
&lt;br /&gt;
As a user who tried out all the latest browsers there are special features I&#039;ve grown to like which should simply be built-in into Firefox.&lt;br /&gt;
Some may argue that you can find an extension for everything, but some novice users simply can&#039;t find those extensions, or even configure them properly.&lt;br /&gt;
&lt;br /&gt;
I will try to form some kind of a proposal for improved tabbed browsing in this section, and once it&#039;s ready I will move this section to [[Firefox:2.0 Tabbed Browsing]]. &lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;: This is still WIP and every now and then I will be adding new things to it.&lt;br /&gt;
&lt;br /&gt;
If you have any comments/suggestions, add them in the [[Talk:Firefox:2.0_Tabbed_Browsing#Users.27_Comments|Comments section]]&lt;br /&gt;
&lt;br /&gt;
=== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ===&lt;br /&gt;
&lt;br /&gt;
Discussed features:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Tabbed Browsing Presets&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Window Modes&#039;&#039;&#039;&lt;br /&gt;
* Tab Behaviour&lt;br /&gt;
** Focus Settings&lt;br /&gt;
* Tab Appearance &lt;br /&gt;
* &#039;&#039;&#039;Tab Groups&#039;&#039;&#039;&lt;br /&gt;
* Tab Sessions&lt;br /&gt;
* Tab History (Last Opened Tabs for the current session)&lt;br /&gt;
* Extensions&lt;br /&gt;
&lt;br /&gt;
=== In Detail ===&lt;br /&gt;
&lt;br /&gt;
==== Tabbed Browsing Presets ====&lt;br /&gt;
A preset is a set of prefs and their values. The preset will only contains prefs that modify the tabbed browsing configuration.&lt;br /&gt;
This will allow us to ship Firefox with preconfigured presets (Legacy Preset and Modern Preset).&lt;br /&gt;
The Legay Preset will be configured to have the same functionality that Firefox 1.0 offered (for those who still prefer it), and the Modern Preset will be configured for the optimal tabbed browsing experience (should be turned on by default).&lt;br /&gt;
&lt;br /&gt;
==== Window Modes ====&lt;br /&gt;
Firefox should support 3 types of window modes:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use Multiple Windows&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this mode any action that is set to open a new window, will do so. Of course, the user can still force to open in a new tab via a middle-click, or any other shortcut he sets for &amp;quot;open in a new tab&amp;quot;.&lt;br /&gt;
This should be a part of the Firefox Legacy Preset.&lt;br /&gt;
: Note: Starting another Firefox process should open a new window pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use Multiple Windows when Forced&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this mode windows will only be opened explicitly (by user request). Any action that should want to open a new window, will open it in a new tab instead, unless the user explicitly wants it in a new window (Example: For links, Right Click -&amp;gt; Open in a new Window).&lt;br /&gt;
: Note: Starting another Firefox process should open a new window pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use a Single Window&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This mode will force any action that opens a new window to open in a new tab. Firefox cannot have multiple instances open (unless it&#039;s a different version of Firefox that&#039;s open).&lt;br /&gt;
&#039;This mode should also disable/remove any menu items that say &amp;quot;Open in a New Window&amp;quot;.&lt;br /&gt;
: Note: Starting another Firefox process should open a new tab pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Tab Grouping ====&lt;br /&gt;
Tab Grouping is a way to identify a group of tabs as one. There might be several uses for this feature, but at the moment it should be the lowest of priorities (unless users vote for it).&lt;br /&gt;
There&#039;s not much to say, except describe the configuration of this feature, so here are the prefs for it:&lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;&#039;Tab Grouping Preferences&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;General&#039;&#039;&#039;:&lt;br /&gt;
* Tab Groups - Enabled/Disabled&lt;br /&gt;
** This simply enabled/disabled the feature altogether.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Group tabs by&#039;&#039;&#039;:&lt;br /&gt;
* Location (All tabs originitating from the same website are grouped)&lt;br /&gt;
* &amp;lt;Need more ideas&amp;gt;&amp;lt;br&amp;gt;&#039;&#039;&#039;Note&#039;&#039;&#039;: that there are things that override this, such as the Open as Tab Group feature in the Bookmarks&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Identify groups by&#039;&#039;&#039;:&lt;br /&gt;
* Number&lt;br /&gt;
* Colour&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Misc&#039;&#039;&#039;:&lt;br /&gt;
* Only one active group at a time.&lt;br /&gt;
** This feature will reduce the clutter of having many tabs open by collapsing a group of tabs into one when you focus another group.&amp;lt;br&amp;gt;When you select a collapsed group of tabs, the group expands by showing all the tabs in that group (and the previous groups collapses), and the tab that was previously focused will retain its focus.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
When Tab Grouping is enabled, two new items are added to the Bookmarks menus:&lt;br /&gt;
* Open as Tab Group&lt;br /&gt;
* Bookmark Tab Group (similar to the Bookmark tabs in one folder)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;: Any new tab will be opened after the last tab of the currently focused group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Things to consider adding&amp;lt;/u&amp;gt;:&lt;br /&gt;
* Allow custom tab groups, so even that you have a few pages from the same website open, you can have them in different groups.&lt;br /&gt;
&lt;br /&gt;
=== Users&#039; Comments ===&lt;br /&gt;
* Your comments here&lt;br /&gt;
* And here...&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5591</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5591"/>
		<updated>2005-04-25T15:05:45Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Caleb&amp;#039;s Proposal */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
=== Intro ===&lt;br /&gt;
&lt;br /&gt;
Firefox only offers very basic tabbed browsing functionality, something that must be addressed before 2.0 (Of cousre some features can be pushed back to 2.0).&lt;br /&gt;
&lt;br /&gt;
As a user who tried out all the latest browsers there are special features I&#039;ve grown to like which should simply be built-in into Firefox.&lt;br /&gt;
Some may argue that you can find an extension for everything, but some novice users simply can&#039;t find those extensions, or even configure them properly.&lt;br /&gt;
&lt;br /&gt;
I will try to form some kind of a proposal for improved tabbed browsing in this section, and once it&#039;s ready I will move this section to [[Firefox:2.0 Tabbed Browsing]]. Note: This is still WIP and every now and then I will be adding new things to it.&lt;br /&gt;
&lt;br /&gt;
=== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ===&lt;br /&gt;
&lt;br /&gt;
Discussed features:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Tabbed Browsing Presets&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Window Modes&#039;&#039;&#039;&lt;br /&gt;
* Tab Behaviour&lt;br /&gt;
** Focus Settings&lt;br /&gt;
* Tab Appearance &lt;br /&gt;
* &#039;&#039;&#039;Tab Groups&#039;&#039;&#039;&lt;br /&gt;
* Tab Sessions&lt;br /&gt;
* Tab History (Last Opened Tabs for the current session)&lt;br /&gt;
* Extensions&lt;br /&gt;
&lt;br /&gt;
=== In Detail ===&lt;br /&gt;
&lt;br /&gt;
==== Tabbed Browsing Presets ====&lt;br /&gt;
A preset is a set of prefs and their values. The preset will only contains prefs that modify the tabbed browsing configuration.&lt;br /&gt;
This will allow us to ship Firefox with preconfigured presets (Legacy Preset and Modern Preset).&lt;br /&gt;
The Legay Preset will be configured to have the same functionality that Firefox 1.0 offered (for those who still prefer it), and the Modern Preset will be configured for the optimal tabbed browsing experience (should be turned on by default).&lt;br /&gt;
&lt;br /&gt;
==== Window Modes ====&lt;br /&gt;
Firefox should support 3 types of window modes:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use Multiple Windows&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this mode any action that is set to open a new window, will do so. Of course, the user can still force to open in a new tab via a middle-click, or any other shortcut he sets for &amp;quot;open in a new tab&amp;quot;.&lt;br /&gt;
This should be a part of the Firefox Legacy Preset.&lt;br /&gt;
: Note: Starting another Firefox process should open a new window pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use Multiple Windows when Forced&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this mode windows will only be opened explicitly (by user request). Any action that should want to open a new window, will open it in a new tab instead, unless the user explicitly wants it in a new window (Example: For links, Right Click -&amp;gt; Open in a new Window).&lt;br /&gt;
: Note: Starting another Firefox process should open a new window pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use a Single Window&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This mode will force any action that opens a new window to open in a new tab. Firefox cannot have multiple instances open (unless it&#039;s a different version of Firefox that&#039;s open).&lt;br /&gt;
&#039;This mode should also disable/remove any menu items that say &amp;quot;Open in a New Window&amp;quot;.&lt;br /&gt;
: Note: Starting another Firefox process should open a new tab pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Tab Grouping ====&lt;br /&gt;
Tab Grouping is a way to identify a group of tabs as one. There might be several uses for this feature, but at the moment it should be the lowest of priorities (unless users vote for it).&lt;br /&gt;
There&#039;s not much to say, except describe the configuration of this feature, so here are the prefs for it:&lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;&#039;Tab Grouping Preferences&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;General&#039;&#039;&#039;:&lt;br /&gt;
* Tab Groups - Enabled/Disabled&lt;br /&gt;
** This simply enabled/disabled the feature altogether.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Group tabs by&#039;&#039;&#039;:&lt;br /&gt;
* Location (All tabs originitating from the same website are grouped)&lt;br /&gt;
* &amp;lt;Need more ideas&amp;gt;&amp;lt;br&amp;gt;&#039;&#039;&#039;Note&#039;&#039;&#039;: that there are things that override this, such as the Open as Tab Group feature in the Bookmarks&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Identify groups by&#039;&#039;&#039;:&lt;br /&gt;
* Number&lt;br /&gt;
* Colour&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Misc&#039;&#039;&#039;:&lt;br /&gt;
* Only one active group at a time.&lt;br /&gt;
** This feature will reduce the clutter of having many tabs open by collapsing a group of tabs into one when you focus another group.&amp;lt;br&amp;gt;When you select a collapsed group of tabs, the group expands by showing all the tabs in that group (and the previous groups collapses), and the tab that was previously focused will retain its focus.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
When Tab Grouping is enabled, two new items are added to the Bookmarks menus:&lt;br /&gt;
* Open as Tab Group&lt;br /&gt;
* Bookmark Tab Group (similar to the Bookmark tabs in one folder)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;: Any new tab will be opened after the last tab of the currently focused group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Things to consider adding&amp;lt;/u&amp;gt;:&lt;br /&gt;
* Allow custom tab groups, so even that you have a few pages from the same website open, you can have them in different groups.&lt;br /&gt;
&lt;br /&gt;
=== Users&#039; Comments ===&lt;br /&gt;
* Your comments here&lt;br /&gt;
* And here...&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5590</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5590"/>
		<updated>2005-04-25T14:45:09Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Tabbed Browsing Proposal for 2.0 (&amp;#039;&amp;#039;&amp;#039;Work In Progress&amp;#039;&amp;#039;&amp;#039;) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
=== Intro ===&lt;br /&gt;
&lt;br /&gt;
Firefox only offers very basic tabbed browsing functionality, something that must be addressed before 2.0 (Of cousre some features can be pushed back to 2.0).&lt;br /&gt;
&lt;br /&gt;
As a user who tried out all the latest browsers there are special features I&#039;ve grown to like which should simply be built-in into Firefox.&lt;br /&gt;
Some may argue that you can find an extension for everything, but some novice users simply can&#039;t find those extensions, or even configure them properly.&lt;br /&gt;
&lt;br /&gt;
I will try to form some kind of a proposal for improved tabbed browsing in this section, and once it&#039;s ready I will move this section to [[Firefox:2.0 Tabbed Browsing]]. Note: This is still WIP and every now and then I will be adding new things to it.&lt;br /&gt;
&lt;br /&gt;
=== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ===&lt;br /&gt;
&lt;br /&gt;
Discussed features:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Tabbed Browsing Presets&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Window Modes&#039;&#039;&#039;&lt;br /&gt;
* Tab Behaviour&lt;br /&gt;
** Focus Settings&lt;br /&gt;
* Tab Appearance &lt;br /&gt;
* &#039;&#039;&#039;Tab Groups&#039;&#039;&#039;&lt;br /&gt;
* Tab Sessions&lt;br /&gt;
* Tab History (Last Opened Tabs for the current session)&lt;br /&gt;
* Extensions&lt;br /&gt;
&lt;br /&gt;
=== In Detail ===&lt;br /&gt;
&lt;br /&gt;
==== Tabbed Browsing Presets ====&lt;br /&gt;
A preset is a set of prefs and their values. The preset will only contains prefs that modify the tabbed browsing configuration.&lt;br /&gt;
This will allow us to ship Firefox with preconfigured presets (Legacy Preset and Modern Preset).&lt;br /&gt;
The Legay Preset will be configured to have the same functionality that Firefox 1.0 offered (for those who still prefer it), and the Modern Preset will be configured for the optimal tabbed browsing experience (should be turned on by default).&lt;br /&gt;
&lt;br /&gt;
==== Window Modes ====&lt;br /&gt;
Firefox should support 3 types of window modes:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use Multiple Windows&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this mode any action that is set to open a new window, will do so. Of course, the user can still force to open in a new tab via a middle-click, or any other shortcut he sets for &amp;quot;open in a new tab&amp;quot;.&lt;br /&gt;
This should be a part of the Firefox Legacy Preset.&lt;br /&gt;
: Note: Starting another Firefox process should open a new window pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use Multiple Windows when Forced&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this mode windows will only be opened explicitly (by user request). Any action that should want to open a new window, will open it in a new tab instead, unless the user explicitly wants it in a new window (Example: For links, Right Click -&amp;gt; Open in a new Window).&lt;br /&gt;
: Note: Starting another Firefox process should open a new window pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use a Single Window&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This mode will force any action that opens a new window to open in a new tab. Firefox cannot have multiple instances open (unless it&#039;s a different version of Firefox that&#039;s open).&lt;br /&gt;
&#039;This mode should also disable/remove any menu items that say &amp;quot;Open in a New Window&amp;quot;.&lt;br /&gt;
: Note: Starting another Firefox process should open a new tab pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Tab Grouping ====&lt;br /&gt;
Tab Grouping is a way to identify a group of tabs as one. There might be several uses for this feature, but at the moment it should be the lowest of priorities (unless users vote for it).&lt;br /&gt;
There&#039;s not much to say, except describe the configuration of this feature, so here are the prefs for it:&lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;&#039;Tab Grouping Preferences&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;General&#039;&#039;&#039;:&lt;br /&gt;
* Tab Groups - Enabled/Disabled&lt;br /&gt;
** This simply enabled/disabled the feature altogether.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Group tabs by&#039;&#039;&#039;:&lt;br /&gt;
* Location (All tabs originitating from the same website are grouped)&lt;br /&gt;
* &amp;lt;Need more ideas&amp;gt;&amp;lt;br&amp;gt;&#039;&#039;&#039;Note&#039;&#039;&#039;, that there are things that override this, such as the Open as Tab Group feature in the Bookmarks&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Identify groups by&#039;&#039;&#039;:&lt;br /&gt;
* Number&lt;br /&gt;
* Colour&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Misc&#039;&#039;&#039;:&lt;br /&gt;
* Only one active group at a time.&lt;br /&gt;
** This feature will reduce the clutter of having many tabs open by collapsing a group of tabs into one when you focus another group.&amp;lt;br&amp;gt;When you select a collapsed group of tabs, the group expands by showing all the tabs in that group (and the previous groups collapses), and the tab that was previously focused will retain its focus.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
When Tab Grouping is enabled, two new items are added to the Bookmarks menus:&lt;br /&gt;
* Open as Tab Group&lt;br /&gt;
* Bookmark Tab Group (similar to the Bookmark tabs in one folder)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;: Any new tab will be opened after the last tab of the currently focused group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Things to consider adding&amp;lt;/u&amp;gt;:&lt;br /&gt;
* Allow custom tab groups, so even that you have a few pages from the same website open, you can have them in different groups.&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5589</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5589"/>
		<updated>2005-04-25T14:40:41Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Caleb&amp;#039;s Proposal */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
=== Intro ===&lt;br /&gt;
&lt;br /&gt;
Firefox only offers very basic tabbed browsing functionality, something that must be addressed before 2.0 (Of cousre some features can be pushed back to 2.0).&lt;br /&gt;
&lt;br /&gt;
As a user who tried out all the latest browsers there are special features I&#039;ve grown to like which should simply be built-in into Firefox.&lt;br /&gt;
Some may argue that you can find an extension for everything, but some novice users simply can&#039;t find those extensions, or even configure them properly.&lt;br /&gt;
&lt;br /&gt;
I will try to form some kind of a proposal for improved tabbed browsing in this section, and once it&#039;s ready I will move this section to [[Firefox:2.0 Tabbed Browsing]]. Note: This is still WIP and every now and then I will be adding new things to it.&lt;br /&gt;
&lt;br /&gt;
=== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ===&lt;br /&gt;
&lt;br /&gt;
Discussed features:&lt;br /&gt;
&lt;br /&gt;
* Tabbed Browsing Presets&lt;br /&gt;
* Window Modes&lt;br /&gt;
* Tab Behaviour&lt;br /&gt;
** Focus Settings&lt;br /&gt;
* Tab Appearance &lt;br /&gt;
* Tab Groups&lt;br /&gt;
* Tab Sessions&lt;br /&gt;
* Tab History (Last Opened Tabs for the current session)&lt;br /&gt;
* Extensions&lt;br /&gt;
&lt;br /&gt;
=== In Detail ===&lt;br /&gt;
&lt;br /&gt;
==== Tabbed Browsing Presets ====&lt;br /&gt;
A preset is a set of prefs and their values. The preset will only contains prefs that modify the tabbed browsing configuration.&lt;br /&gt;
This will allow us to ship Firefox with preconfigured presets (Legacy Preset and Modern Preset).&lt;br /&gt;
The Legay Preset will be configured to have the same functionality that Firefox 1.0 offered (for those who still prefer it), and the Modern Preset will be configured for the optimal tabbed browsing experience (should be turned on by default).&lt;br /&gt;
&lt;br /&gt;
==== Window Modes ====&lt;br /&gt;
Firefox should support 3 types of window modes:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use Multiple Windows&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this mode any action that is set to open a new window, will do so. Of course, the user can still force to open in a new tab via a middle-click, or any other shortcut he sets for &amp;quot;open in a new tab&amp;quot;.&lt;br /&gt;
This should be a part of the Firefox Legacy Preset.&lt;br /&gt;
: Note: Starting another Firefox process should open a new window pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use Multiple Windows when Forced&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this mode windows will only be opened explicitly (by user request). Any action that should want to open a new window, will open it in a new tab instead, unless the user explicitly wants it in a new window (Example: For links, Right Click -&amp;gt; Open in a new Window).&lt;br /&gt;
: Note: Starting another Firefox process should open a new window pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use a Single Window&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This mode will force any action that opens a new window to open in a new tab. Firefox cannot have multiple instances open (unless it&#039;s a different version of Firefox that&#039;s open).&lt;br /&gt;
&#039;This mode should also disable/remove any menu items that say &amp;quot;Open in a New Window&amp;quot;.&lt;br /&gt;
: Note: Starting another Firefox process should open a new tab pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Tab Grouping ====&lt;br /&gt;
Tab Grouping is a way to identify a group of tabs as one. There might be several uses for this feature, but at the moment it should be the lowest of priorities (unless users vote for it).&lt;br /&gt;
There&#039;s not much to say, except describe the configuration of this feature, so here are the prefs for it:&lt;br /&gt;
----&lt;br /&gt;
&#039;&#039;&#039;Tab Grouping Preferences&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;General&#039;&#039;&#039;:&lt;br /&gt;
* Tab Groups - Enabled/Disabled&lt;br /&gt;
** This simply enabled/disabled the feature altogether.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Group tabs by&#039;&#039;&#039;:&lt;br /&gt;
* Location (All tabs originitating from the same website are grouped)&lt;br /&gt;
* &amp;lt;Need more ideas&amp;gt;&amp;lt;br&amp;gt;&#039;&#039;&#039;Note&#039;&#039;&#039;, that there are things that override this, such as the Open as Tab Group feature in the Bookmarks&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Identify groups by&#039;&#039;&#039;:&lt;br /&gt;
* Number&lt;br /&gt;
* Colour&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Misc&#039;&#039;&#039;:&lt;br /&gt;
* Only one active group at a time.&lt;br /&gt;
** This feature will reduce the clutter of having many tabs open by collapsing a group of tabs into one when you focus another group.&amp;lt;br&amp;gt;When you select a collapsed group of tabs, the group expands by showing all the tabs in that group (and the previous groups collapses), and the tab that was previously focused will retain its focus.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
When Tab Grouping is enabled, two new items are added to the Bookmarks menus:&lt;br /&gt;
* Open as Tab Group&lt;br /&gt;
* Bookmark Tab Group (similar to the Bookmark tabs in one folder)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;: Any new tab will be opened after the last tab of the currently focused group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Things to consider adding&amp;lt;/u&amp;gt;:&lt;br /&gt;
* Allow custom tab groups, so even that you have a few pages from the same website open, you can have them in different groups.&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5588</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5588"/>
		<updated>2005-04-25T14:25:57Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Caleb&amp;#039;s Proposal */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
=== Intro ===&lt;br /&gt;
&lt;br /&gt;
Firefox only offers very basic tabbed browsing functionality, something that must be addressed before 2.0 (Of cousre some features can be pushed back to 2.0).&lt;br /&gt;
&lt;br /&gt;
As a user who tried out all the latest browsers there are special features I&#039;ve grown to like which should simply be built-in into Firefox.&lt;br /&gt;
Some may argue that you can find an extension for everything, but some novice users simply can&#039;t find those extensions, or even configure them properly.&lt;br /&gt;
&lt;br /&gt;
I will try to form some kind of a proposal for improved tabbed browsing in this section, and once it&#039;s ready I will move this section to [[Firefox:2.0 Tabbed Browsing]]. Note: This is still WIP and every now and then I will be adding new things to it.&lt;br /&gt;
&lt;br /&gt;
=== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ===&lt;br /&gt;
&lt;br /&gt;
Discussed features:&lt;br /&gt;
&lt;br /&gt;
* Tabbed Browsing Presets&lt;br /&gt;
* Window Modes&lt;br /&gt;
* Tab Behaviour&lt;br /&gt;
** Focus Settings&lt;br /&gt;
* Tab Appearance &lt;br /&gt;
* Tab Groups&lt;br /&gt;
* Tab Sessions&lt;br /&gt;
* Tab History (Last Opened Tabs for the current session)&lt;br /&gt;
* Extensions&lt;br /&gt;
&lt;br /&gt;
=== In Detail ===&lt;br /&gt;
&lt;br /&gt;
==== Tabbed Browsing Presets ====&lt;br /&gt;
A preset is a set of prefs and their values. The preset will only contains prefs that modify the tabbed browsing configuration.&lt;br /&gt;
This will allow us to ship Firefox with preconfigured presets (Legacy Preset and Modern Preset).&lt;br /&gt;
The Legay Preset will be configured to have the same functionality that Firefox 1.0 offered (for those who still prefer it), and the Modern Preset will be configured for the optimal tabbed browsing experience (should be turned on by default).&lt;br /&gt;
&lt;br /&gt;
==== Window Modes ====&lt;br /&gt;
Firefox should support 3 types of window modes:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use Multiple Windows&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this mode any action that is set to open a new window, will do so. Of course, the user can still force to open in a new tab via a middle-click, or any other shortcut he sets for &amp;quot;open in a new tab&amp;quot;.&lt;br /&gt;
This should be a part of the Firefox Legacy Preset.&lt;br /&gt;
: Note: Starting another Firefox process should open a new window pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use Multiple Windows when Forced&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this mode windows will only be opened explicitly (by user request). Any action that should want to open a new window, will open it in a new tab instead, unless the user explicitly wants it in a new window (Example: For links, Right Click -&amp;gt; Open in a new Window).&lt;br /&gt;
: Note: Starting another Firefox process should open a new window pointing to the user&#039;s homepage.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&#039;&#039;&#039;Use a Single Window&#039;&#039;&#039;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This mode will force any action that opens a new window to open in a new tab. Firefox cannot have multiple instances open (unless it&#039;s a different version of Firefox that&#039;s open).&lt;br /&gt;
&#039;This mode should also disable/remove any menu items that say &amp;quot;Open in a New Window&amp;quot;.&lt;br /&gt;
: Note: Starting another Firefox process should open a new tab pointing to the user&#039;s homepage.&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5587</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5587"/>
		<updated>2005-04-25T14:13:56Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Intro */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
=== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ===&lt;br /&gt;
&lt;br /&gt;
New features at first glance:&lt;br /&gt;
&lt;br /&gt;
* Window Modes&lt;br /&gt;
* Tabbed Browsing Presets&lt;br /&gt;
* Focus Settings&lt;br /&gt;
* Tab Behaviour&lt;br /&gt;
* Tab Appearance&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5586</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5586"/>
		<updated>2005-04-25T08:44:31Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Caleb&amp;#039;s Proposal */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
=== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ===&lt;br /&gt;
&lt;br /&gt;
New features at first glance:&lt;br /&gt;
&lt;br /&gt;
* Window Modes&lt;br /&gt;
* Tabbed Browsing Presets&lt;br /&gt;
* Focus Settings&lt;br /&gt;
* Tab Behaviour&lt;br /&gt;
* Tab Appearance&lt;br /&gt;
&lt;br /&gt;
== Intro ==&lt;br /&gt;
&lt;br /&gt;
Firefox only offers very basic tabbed browsing functionality, something that must be addressed before 2.0 (Of cousre some features can be pushed back to 2.0).&lt;br /&gt;
&lt;br /&gt;
As a user who tried out all the latest browsers there are special features I&#039;ve grown to like which should simply be built-in into Firefox.&lt;br /&gt;
Some may argue that you can find an extension for everything, but some novice users simply can&#039;t find those extensions, or even configure them properly.&lt;br /&gt;
&lt;br /&gt;
I will try to form some kind of a proposal for improved tabbed browsing in this section, and once it&#039;s ready I will move this section to [[Firefox:2.0 Tabbed Browsing]]. Note: This is still WIP and every now and then I will be adding new things to it.&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5580</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5580"/>
		<updated>2005-04-25T08:44:31Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Caleb&amp;#039;s Proposal */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
=== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ===&lt;br /&gt;
&lt;br /&gt;
New features at first glance:&lt;br /&gt;
&lt;br /&gt;
* Window Modes&lt;br /&gt;
* Tabbed Browsing Presets&lt;br /&gt;
* Focus Settings&lt;br /&gt;
* Tab Behaviour&lt;br /&gt;
* Tab Appearance&lt;br /&gt;
&lt;br /&gt;
== Intro ==&lt;br /&gt;
&lt;br /&gt;
Firefox only offers very basic tabbed browsing functionality, something that must be addressed before 2.0 (Of cousre some features can be pushed back to 2.0).&lt;br /&gt;
&lt;br /&gt;
As a user who tried out all the latest browsers there are special features I&#039;ve grown to like which should simply be built-in into Firefox.&lt;br /&gt;
Some may argue that you can find an extension for everything, but some novice users simply can&#039;t find those extensions, or even configure them properly.&lt;br /&gt;
&lt;br /&gt;
I will try to form some kind of a proposal for improved tabbed browsing in this section, and once it&#039;s ready I will move this section to [[Firefox:2.0 Tabbed Browsing]]. Note: This is still WIP and every now and then I will be adding new things to it.&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5579</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5579"/>
		<updated>2005-04-25T08:44:31Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Caleb&amp;#039;s Proposal */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
=== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ===&lt;br /&gt;
&lt;br /&gt;
New features at first glance:&lt;br /&gt;
&lt;br /&gt;
* Window Modes&lt;br /&gt;
* Tabbed Browsing Presets&lt;br /&gt;
* Focus Settings&lt;br /&gt;
* Tab Behaviour&lt;br /&gt;
* Tab Appearance&lt;br /&gt;
&lt;br /&gt;
== Intro ==&lt;br /&gt;
&lt;br /&gt;
Firefox only offers very basic tabbed browsing functionality, something that must be addressed before 2.0 (Of cousre some features can be pushed back to 2.0).&lt;br /&gt;
&lt;br /&gt;
As a user who tried out all the latest browsers there are special features I&#039;ve grown to like which should simply be built-in into Firefox.&lt;br /&gt;
Some may argue that you can find an extension for everything, but some novice users simply can&#039;t find those extensions, or even configure them properly.&lt;br /&gt;
&lt;br /&gt;
I will try to form some kind of a proposal for improved tabbed browsing in this section, and once it&#039;s ready I will move this section to [[Firefox:2.0 Tabbed Browsing]]. Note: This is still WIP and every now and then I will be adding new things to it.&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5578</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5578"/>
		<updated>2005-04-25T08:44:05Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Tabbed Browsing Proposal for 2.0 (&amp;#039;&amp;#039;&amp;#039;Work In Progress&amp;#039;&amp;#039;&amp;#039;) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
== Intro ==&lt;br /&gt;
&lt;br /&gt;
Firefox only offers very basic tabbed browsing functionality, something that must be addressed before 2.0 (Of cousre some features can be pushed back to 2.0).&lt;br /&gt;
&lt;br /&gt;
As a user who tried out all the latest browsers there are special features I&#039;ve grown to like which should simply be built-in into Firefox.&lt;br /&gt;
Some may argue that you can find an extension for everything, but some novice users simply can&#039;t find those extensions, or even configure them properly.&lt;br /&gt;
&lt;br /&gt;
I will try to form some kind of a proposal for improved tabbed browsing in this section, and once it&#039;s ready I will move this section to [[Firefox:2.0 Tabbed Browsing]]. Note: This is still WIP and every now and then I will be adding new things to it.&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5577</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5577"/>
		<updated>2005-04-25T08:34:06Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Caleb&amp;#039;s Proposal */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
== Intro ==&lt;br /&gt;
&lt;br /&gt;
Firefox only offers very basic tabbed browsing functionality, something that must be addressed before 2.0 (Of cousre some features can be pushed back to 2.0).&lt;br /&gt;
&lt;br /&gt;
As a user who tried out all the latest browsers there are special features I&#039;ve grown to like which should simply be built-in into Firefox.&lt;br /&gt;
Some may argue that you can find an extension for everything, but some novice users simply can&#039;t find those extensions, or even configure them properly.&lt;br /&gt;
&lt;br /&gt;
I will try to form some kind of a proposal for improved tabbed browsing in this section, and once it&#039;s ready I will move this section to [[Firefox:2.0 Tabbed Browsing]]. Note: This is still WIP and every now and then I will be adding new things to it.&lt;br /&gt;
&lt;br /&gt;
== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ==&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5576</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5576"/>
		<updated>2005-04-25T08:34:06Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Caleb&amp;#039;s Proposal */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
== Intro ==&lt;br /&gt;
&lt;br /&gt;
Firefox only offers very basic tabbed browsing functionality, something that must be addressed before 2.0 (Of cousre some features can be pushed back to 2.0).&lt;br /&gt;
&lt;br /&gt;
As a user who tried out all the latest browsers there are special features I&#039;ve grown to like which should simply be built-in into Firefox.&lt;br /&gt;
Some may argue that you can find an extension for everything, but some novice users simply can&#039;t find those extensions, or even configure them properly.&lt;br /&gt;
&lt;br /&gt;
I will try to form some kind of a proposal for improved tabbed browsing in this section, and once it&#039;s ready I will move this section to [[Firefox:2.0 Tabbed Browsing]]. Note: This is still WIP and every now and then I will be adding new things to it.&lt;br /&gt;
&lt;br /&gt;
== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ==&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5575</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5575"/>
		<updated>2005-04-25T08:32:47Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Intro */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ==&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5574</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5574"/>
		<updated>2005-04-25T08:31:56Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Caleb&amp;#039;s Proposal */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
== Intro ==&lt;br /&gt;
&lt;br /&gt;
Firefox only offers very basic tabbed browsing functionality, something that must be addressed before 2.0 (Of cousre some features can be pushed back to 2.0).&lt;br /&gt;
&lt;br /&gt;
As a user who tried out all the latest browsers there are special features I&#039;ve grown to like which should simply be built-in into Firefox.&lt;br /&gt;
Some may argue that you can find an extension for everything, but some novice users simply can&#039;t find those extensions, or even configure them properly.&lt;br /&gt;
&lt;br /&gt;
I will try to form some kind of a proposal for improved tabbed browsing in this section, and once it&#039;s ready I will move this section to [[Firefox:2.0 Tabbed Browsing]]. Note: This is still WIP and every now and then I will be adding new things to it.&lt;br /&gt;
&lt;br /&gt;
== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ==&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5573</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5573"/>
		<updated>2005-04-25T08:31:56Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Caleb&amp;#039;s Proposal */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
== Intro ==&lt;br /&gt;
&lt;br /&gt;
Firefox only offers very basic tabbed browsing functionality, something that must be addressed before 2.0 (Of cousre some features can be pushed back to 2.0).&lt;br /&gt;
&lt;br /&gt;
As a user who tried out all the latest browsers there are special features I&#039;ve grown to like which should simply be built-in into Firefox.&lt;br /&gt;
Some may argue that you can find an extension for everything, but some novice users simply can&#039;t find those extensions, or even configure them properly.&lt;br /&gt;
&lt;br /&gt;
I will try to form some kind of a proposal for improved tabbed browsing in this section, and once it&#039;s ready I will move this section to [[Firefox:2.0 Tabbed Browsing]]. Note: This is still WIP and every now and then I will be adding new things to it.&lt;br /&gt;
&lt;br /&gt;
== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ==&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5572</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5572"/>
		<updated>2005-04-25T08:31:11Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Intro */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ==&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5571</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5571"/>
		<updated>2005-04-25T08:23:36Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Why not use the back button? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). --[[User:Caleb|Caleb]] 01:23, 25 Apr 2005 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
== Intro ==&lt;br /&gt;
&lt;br /&gt;
Firefox only offers very basic tabbed browsing functionality, something that must be addressed before 2.0 (Of cousre some features can be pushed back to 2.0).&lt;br /&gt;
&lt;br /&gt;
As a user who tried out all the latest browsers there are special features I&#039;ve grown to like which should simply be built-in into Firefox.&lt;br /&gt;
Some may argue that you can find an extension for everything, but some novice users simply can&#039;t find those extensions, or even configure them properly.&lt;br /&gt;
&lt;br /&gt;
I will try to form some kind of a proposal for improved tabbed browsing in this section, and once it&#039;s ready I will move this section to [[Firefox:2.0 Tabbed Browsing]]. Note: This is still WIP and every now and then I will be adding new things to it.&lt;br /&gt;
&lt;br /&gt;
== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ==&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5570</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5570"/>
		<updated>2005-04-25T08:21:24Z</updated>

		<summary type="html">&lt;p&gt;Caleb: Caleb&amp;#039;s Proposal&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). [[User:Caleb|Caleb]] 11:08, 25 Apr 2005 (GMT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Caleb&#039;s Proposal ==&lt;br /&gt;
&lt;br /&gt;
== Intro ==&lt;br /&gt;
&lt;br /&gt;
Firefox only offers very basic tabbed browsing functionality, something that must be addressed before 2.0 (Of cousre some features can be pushed back to 2.0).&lt;br /&gt;
&lt;br /&gt;
As a user who tried out all the latest browsers there are special features I&#039;ve grown to like which should simply be built-in into Firefox.&lt;br /&gt;
Some may argue that you can find an extension for everything, but some novice users simply can&#039;t find those extensions, or even configure them properly.&lt;br /&gt;
&lt;br /&gt;
I will try to form some kind of a proposal for improved tabbed browsing in this section, and once it&#039;s ready I will move this section to [[Firefox:2.0 Tabbed Browsing]]. Note: This is still WIP and every now and then I will be adding new things to it.&lt;br /&gt;
&lt;br /&gt;
== Tabbed Browsing Proposal for 2.0 (&#039;&#039;&#039;Work In Progress&#039;&#039;&#039;) ==&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5569</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5569"/>
		<updated>2005-04-25T08:09:54Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Why not use the back button? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse. For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). [[User:Caleb|Caleb]] 11:08, 25 Apr 2005 (GMT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5568</id>
		<title>Talk:Firefox:3.0 Tabbed Browsing</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Talk:Firefox:3.0_Tabbed_Browsing&amp;diff=5568"/>
		<updated>2005-04-25T08:09:34Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Why not use the back button? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Tab HTML Tag ==&lt;br /&gt;
&lt;br /&gt;
This is probably a discussion that doesn&#039;t only belong here, but also at the W3C; how about making Firefox react to a new specification within the anchor tag? I&#039;m just going to give an example that should be very clear: &amp;amp;lt;A HREF=&amp;quot;link&amp;quot; TARGET=_TAB&amp;amp;gt;...&lt;br /&gt;
I don&#039;t think there&#039;s any use in further explanation!&lt;br /&gt;
--[[User:Xavez|Xavez]] 06:39, 26 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Per-tab close button ==&lt;br /&gt;
&lt;br /&gt;
Does &amp;quot;close button on tabs&amp;quot; mean a per-tab close button?  This seems like a usability issue to me - gaim does this, and it&#039;s much too easy to unintentionally close a tab.&lt;br /&gt;
--[[User:CTho|CTho]] 11:39, 28 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== on tabbed browsing ==&lt;br /&gt;
&lt;br /&gt;
I wrote some thoughts in the [[Firefox:Tabbed_Browsing:Scratch_Pad]] that I believe should be taken into consideration when talking about improvements to Tabbed Browsing. cheers. -- [[User:AlliXSenoS|AlliXSenoS]] 18:16, 30 Jan 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
== Why not use the back button? ==&lt;br /&gt;
&lt;br /&gt;
This is an idea I had that I think might work. Imagine single-window mode is on (since we are discussing tabs), and a user clicks a link that opens in a new tab. We could leave the back button enabled so if the user clicks the back button, the tab closes and firefox returns to the tab that page came from. The same could apply to new windows from links, when a new window opens, click the back button (or press backspace) to close the window and go back to the page that opened it. &lt;br /&gt;
&lt;br /&gt;
This will benefit beginner users because they can sometimes be lost by randomly placed new-window links and plus it means I can easily close a lot of tabs and windows with just the backspace button. &lt;br /&gt;
&lt;br /&gt;
Any thoughts on this?&lt;br /&gt;
&lt;br /&gt;
*As a user, I must agree - the back button isn&#039;t enabled in that case, and enabling it this way would give it the natural meaning. [[User:Tobu|Tobu]] 06:17, 13 Mar 2005 (PST)&lt;br /&gt;
&lt;br /&gt;
* I strongly disagree. People already grasp the meaning of &amp;quot;back&amp;quot;. And having &amp;quot;back&amp;quot; do different things on different tabs will only make matters worse.&lt;br /&gt;
For example, in one tab &amp;quot;back&amp;quot; would go to the previous page, and on th eother tab it would close it and focus the page that opened it (_if_ it still exists). [[User:Caleb|Caleb]] 11:08, 25 Apr 2005 (GMT)&lt;br /&gt;
&lt;br /&gt;
== Complex Solution ==&lt;br /&gt;
I must admit I sometimes close a tab by an accident. I IMO think, that&#039;s because:&lt;br /&gt;
1. The tab-close button is &amp;quot;shared&amp;quot; and stands at the same point when other tab gets focus after closing the current tab.&lt;br /&gt;
2. It takes time to distinguish which tab has focus since the non-focused tabs are not dimmed.&lt;br /&gt;
&lt;br /&gt;
As a remedy, I&#039;d suggest to go the way Eclipse manages its tabs, ie. when hovering over a tab, a close button icon appears on it. At least, this would eliminate the issue at point 1. To improve the focused tab distinction as described at point 2, I&#039;d suggest do dimm all the tabs that don&#039;t have focus.&lt;br /&gt;
&lt;br /&gt;
When it comes to the Tobu&#039;s suggestion of using back button, I think it&#039;s great idea as it tracks the history accross the tabs. That would necessarilly make history more complicated since a linear row of URLs wouldn&#039;t be enough in this case. Instead, a tree of URLs, branching for each new tab would have to be maintained. If realized, I&#039;d suggest to change colour of the back button when closing the current tab and switching to the &amp;quot;parent&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
As an addition, a solution to the missing progress bar for unfocused tabs, I&#039;d preffer an improved throber - a rotating (indicates &amp;quot;still in progress&amp;quot;) filling pie diagram of the throbber size. This solution would take up much less space on a tab in comparison to the common progress bar. When hovering such a tab, a tooltip shows the exact percentage of the progress.&lt;br /&gt;
Any toghts?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
See [[Firefox:2.0 Tabbed Browsing]].&lt;br /&gt;
--[[User:FunTomas|funTomas]] 13:16, 13 Mar 2005 (PST)&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Firefox:Tabbed_Browsing:Scratch_Pad&amp;diff=10990</id>
		<title>Firefox:Tabbed Browsing:Scratch Pad</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Firefox:Tabbed_Browsing:Scratch_Pad&amp;diff=10990"/>
		<updated>2005-04-25T08:04:22Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Single window mode */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== What&#039;s missing in 1.0? by [[User:AlliXSenoS|AlliXSenoS]] ==&lt;br /&gt;
&lt;br /&gt;
This is my first ever Wiki page so excuse my lack of skill ;)&lt;br /&gt;
&lt;br /&gt;
I&#039;m here to say what I need from tabbed browsing in firefox and don&#039;t get from the vanilla version. I use [http://piro.sakura.ne.jp/xul/tabextensions/index.html.en TBE] (I know most of you frown upon hearing it&#039;s name) for that extra oomph. So what DOES TBE actually bring into the picture that&#039;s actually worth talking about?&lt;br /&gt;
&lt;br /&gt;
Here it is:&lt;br /&gt;
* the ability to force single window mode&lt;br /&gt;
* customizable tabbar actions&lt;br /&gt;
* minor UI customizations&lt;br /&gt;
&lt;br /&gt;
=== Single window mode ===&lt;br /&gt;
&lt;br /&gt;
I&#039;ve been waiting for this since forever. No more taskbar clutter. Yay!&lt;br /&gt;
&lt;br /&gt;
Single window mode means: tabbar always visible, everything and anything that would open in a new window (be it a full interface window or just a popup) opens in a new tab&lt;br /&gt;
&lt;br /&gt;
Single window mode should definitely be a built-in feature (but not something that can&#039;t be turned off... it doesn&#039;t even have to be on by default), it is a real time saver.&lt;br /&gt;
&lt;br /&gt;
Options for single window mode should include a way to define which actions result in a new background tab, new foreground tab or new bg tab which grabs focus when it&#039;s fully loaded (I don&#039;t think anywone in their right mind would use this, but hey, who am I to judge?). the list includes:&lt;br /&gt;
* links&lt;br /&gt;
* opening another instance of Firefox&lt;br /&gt;
* links with target=&amp;quot;_blank&amp;quot;&lt;br /&gt;
* bookmarks&lt;br /&gt;
* bookmarks toolbar&lt;br /&gt;
* history&lt;br /&gt;
* javascript popups&lt;br /&gt;
&lt;br /&gt;
each of these (except, well, the last one ;) ) can be activated by a normal (left) click or a wheel (mid) click. these should be two different actions.&lt;br /&gt;
&lt;br /&gt;
=== Customizable tabbar actions ===&lt;br /&gt;
&lt;br /&gt;
I configure TBE as follows:&lt;br /&gt;
* tab dbl click = duplicate tab&lt;br /&gt;
* tab mid click = close tab&lt;br /&gt;
* tab bar dbl click = new blank tab&lt;br /&gt;
* tab bar mid click = undo close tab&lt;br /&gt;
&lt;br /&gt;
these can, of course, be modified (and this is not the default setup)... there is a whole range of settings for these four actions: reload, move, close all to the left, close all to the right, close all other, close all...&lt;br /&gt;
&lt;br /&gt;
Also, one VERY IMPORTANT thing. Switching tabs with the scroll wheel. Eternal blessings to the deity that invented that. It should most definitely be part of firefox.&lt;br /&gt;
&lt;br /&gt;
=== minor UI customizations ===&lt;br /&gt;
&lt;br /&gt;
The tabbar close button - awful... the per-tab close button some extensions create - even more awful. I&#039;ve never clicked either one since the day I started using firefox. I can see how some people might find it useful so it&#039;s ok to leave it there by default. But there should be an option to remove it (them).&lt;br /&gt;
&lt;br /&gt;
TBE also has a feature that shows a progress bar in the tabs while they&#039;re loading. This is great for opening up a ton of links in the background.&lt;br /&gt;
&lt;br /&gt;
Ehh... that&#039;s all from me. I don&#039;t come here often, so please contact me for further discussion at [mailto:allixsenos@gmail.com allixsenos@gmail.com]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Comments [[Bugmenot]] ===&lt;br /&gt;
&lt;br /&gt;
* For 1.1, we should fix up the hidden popup-to-tab prefs and make those prefs available to the general public&lt;br /&gt;
* For 1.5, we should consider adding additional &amp;quot;open in new tab/window&amp;quot; prefs to allow the user to open bookmarks, history, external site link, internal program link (eg. the u.m.o link on the extension manager, the external links in the help file as well as the links in extensions), urlbar and search queries (both from the searchbar and the context menu) into new tabs/windows&lt;br /&gt;
* Drag and drop reordering of tabs is also an important feature and it doesn&#039;t add additional UI/pref clutter&lt;br /&gt;
* We could also consider adding highlighting for unread tabs&lt;br /&gt;
* Better progress indications would also be nice&lt;br /&gt;
* Things like per-tab close button, tab clicking options are better left for extension writers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Comments [[Grauw]] ===&lt;br /&gt;
&lt;br /&gt;
DOs:&lt;br /&gt;
* &#039;Single Window Mode&#039; options are already present in current nightly builds and even Firefox 1.0 (although as a hidden pref, because there are some bugs).&lt;br /&gt;
* Tab dragging is another important feature which should be there, it gives the user the ability to organise their tabs better, useful when you have many.&lt;br /&gt;
* Make tabs not disappear when the tabbar is full. A collector was suggested, which sounds good.&lt;br /&gt;
&lt;br /&gt;
DON’Ts:&lt;br /&gt;
* Per-tab close buttons are always a bad idea. Some reasons:&lt;br /&gt;
** You can already close with middle-clicking which is much faster and easier&lt;br /&gt;
** They are always small and difficult to click at&lt;br /&gt;
** You always click on them when you didn&#039;t intend to&lt;br /&gt;
** Closing multiple tabs requires the movement of your mouse&lt;br /&gt;
** They take up unnecessary space&lt;br /&gt;
** Believe me, I am using Eclipse, and from that experience I can say that on-tab-closebuttons are a bad idea, except for the ultra-good-hand-eye-coordination computer nerds :).&lt;br /&gt;
* Tab clicking options sound like bloat to me. The presence of those options were also much criticised in the ‘Netscape 8’ browser.&lt;br /&gt;
* Don’t switch tabs with the scrollwheel. I had this in another application and it was annoying as hell. You use the scroll wheel extensively for what it is for, scrolling pages, and you don&#039;t always keep an eye on the exact position of your mouse cursor. As a matter of fact, you usually keep it close to one of the edges of your document area, out of the way of the page content you are trying to read. Accidentally moving it over the tab bar is then easily done by accident.&lt;br /&gt;
&lt;br /&gt;
=== Comments [[User:Kroc|Kroc Camen]] ===&lt;br /&gt;
Please view my comments at http://wiki.mozilla.org/Talk:Firefox:2.0_Tabbed_Browsing&lt;br /&gt;
&amp;quot;Use the back button&amp;quot;&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Firefox:Places:Scratch_Pad&amp;diff=6869</id>
		<title>Firefox:Places:Scratch Pad</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Firefox:Places:Scratch_Pad&amp;diff=6869"/>
		<updated>2005-04-25T05:41:05Z</updated>

		<summary type="html">&lt;p&gt;Caleb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Back to [[Firefox:2.0 PRD]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
       +-----------------------+&lt;br /&gt;
       | / Places              |&lt;br /&gt;
+------+                       +--------------------------------------------------------+&lt;br /&gt;
| +------------------------+                             Search: [                ] (=O)|&lt;br /&gt;
| |                        | +--------------------------------------------------------+ |&lt;br /&gt;
| |                        | |                                                        | |&lt;br /&gt;
| | All Bookmarks          | |                                                        | |&lt;br /&gt;
| | Bookmarks Toolbar      | |                                                        | |&lt;br /&gt;
| | My Shared Links        | |                                                        | |&lt;br /&gt;
| | Asa&#039;s Shared Links     | |                                                        | |&lt;br /&gt;
| | Top Rated              | |                                                        | |&lt;br /&gt;
| | Most Visited           | |                                                        | |&lt;br /&gt;
| | v History              | |                                                        | |&lt;br /&gt;
| |   Today                | |                                                        | |&lt;br /&gt;
| |   Yesterday            | |                                                        | |&lt;br /&gt;
| |   2 days ago           | |                                                        | |&lt;br /&gt;
| |   3 days ago           | |                                                        | |&lt;br /&gt;
| |   Older than 3 days    | |                                                        | |&lt;br /&gt;
| | C:Cars                 | |                                                        | |&lt;br /&gt;
| | C:Work                 | |                                                        | |&lt;br /&gt;
| | C:Goats                | |                                                        | |&lt;br /&gt;
| | F:Stuff                | |                                                        | |&lt;br /&gt;
| |                        | |                                                        | |&lt;br /&gt;
| |                        | |                                                        | |&lt;br /&gt;
| +------------------------+ +--------------------------------------------------------+ |&lt;br /&gt;
|  (+) (-)                    (+) (-)                                   View: (= | Tr)  |&lt;br /&gt;
+---------------------------------------------------------------------------------------+&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Publish to RSS ([http://del.icio.us del.icio.us]-like service)&lt;br /&gt;
* Update Checking&lt;br /&gt;
* Auto-categorization (?)&lt;br /&gt;
* much, much more.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Comments [[jasonlustig]] ===&lt;br /&gt;
&lt;br /&gt;
I like the idea of &amp;quot;shared bookmarks/links&amp;quot;, we should also have the ability to share them over a LAN using [http://developer.apple.com/macosx/rendezvous/ Apple&#039;s Rendezvous]. That way, for example, when going to my friends&#039; computers to show them something i can just pull it up in their view of &amp;quot;Jason&#039;s Shared Bookmarks&amp;quot; or something, similar to itunes&#039; shared music.&lt;br /&gt;
&lt;br /&gt;
=== Comments [[Jesse]] ===&lt;br /&gt;
&lt;br /&gt;
I love del.icio.us.  I use it much more effectively than I ever used bookmarks, but I&#039;m not sure why.  It might be because del.icio.us uses labels instead of folders.  It might be because my del.icio.us bookmarks are public, which forces me to put enough effort into the categorization and description that it still makes sense to me a month later.&lt;br /&gt;
&lt;br /&gt;
http://www.plasticbag.org/archives/2004/10/towards_tagbased_bookmark_management_in_web_browsers.shtml argues for tags/labels in bookmarks.&lt;br /&gt;
&lt;br /&gt;
=== Comments [[Torisugari]] ===&lt;br /&gt;
&lt;br /&gt;
&amp;gt; Auto-categorization (?)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Picking up some words form &amp;lt;meta name=&amp;quot;keywords&amp;quot;&amp;gt; tag. e.g. http://www.mozilla.org/ keywords are &amp;quot;web browser&amp;quot;, &amp;quot;mozilla&amp;quot;, &amp;quot;firefox&amp;quot;, &amp;quot;camino&amp;quot;, &amp;quot;thunderbird&amp;quot;, &amp;quot;bugzilla&amp;quot;, &amp;quot;user agent&amp;quot; and &amp;quot;email client&amp;quot;.&lt;br /&gt;
* Creating some filter a la mail filter. e.g. Has the words:|car| append &amp;quot;Cars&amp;quot; label.&lt;br /&gt;
* Bayesian filter? http://www.mozilla.org/mailnews/arch/spam/ This is really exciting, but maybe too geeky for some.&lt;br /&gt;
&lt;br /&gt;
=== Comments [[Bugmenot]] ===&lt;br /&gt;
&lt;br /&gt;
* Also, the sidebar needs to be enhanced to be able to either float on top of the content (instead of resizing the content area) or to extend outward instead of inward.&lt;br /&gt;
&lt;br /&gt;
=== Comments [[AlexBishop]] ===&lt;br /&gt;
&lt;br /&gt;
[http://wp.netscape.com/browsers/future/aurora.html Aurora], is that you?&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Firefox:2.0_Multi-locale_Installers&amp;diff=11246</id>
		<title>Firefox:2.0 Multi-locale Installers</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Firefox:2.0_Multi-locale_Installers&amp;diff=11246"/>
		<updated>2005-04-25T05:34:59Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Caleb&amp;#039;s Comments */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Synopsis ==&lt;br /&gt;
When we ship the Firefox product currently, we can only fit one locale per installer which leads to duplicating the same binary code for multiple locales.  If we could fit more than one locale per installer, we could place ourselves in a much better situation where a 20-locale Firefox installer may be ~20 MB instead of 100 MB.  Since we ship 3 platforms, that takes our total size from 300 MB to 60 MB.&lt;br /&gt;
&lt;br /&gt;
This is the difference between shipping Firefox, Thunderbird, and Suite on the same CD, or having to split them up onto multiple CDs.&lt;br /&gt;
&lt;br /&gt;
=== Shishen&#039;s Comments ===&lt;br /&gt;
&lt;br /&gt;
Not only the installer should be multi-locale but the installed software too. Given Firefox runs on multi-users systems, each user might prefer to use Firefox in his own language.&lt;br /&gt;
&lt;br /&gt;
=== Caleb&#039;s Comments ===&lt;br /&gt;
&lt;br /&gt;
It would be great if the strings would be external, so if say, there&#039;s a minor security update coming up, users with locales other than en-US could apply the security fix without having to wait for a version of Firefox in their locale.&lt;br /&gt;
Since after all, incremental security updates are not allowed to change anything major in the interface, and even if they do, the patch could be applied in en-US first (not localizing the new strings, but leaving the old ones intact) and when a language pack is available it will update the rest of the strings.&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Firefox:1.5_Download_Manager&amp;diff=8905</id>
		<title>Firefox:1.5 Download Manager</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Firefox:1.5_Download_Manager&amp;diff=8905"/>
		<updated>2005-04-23T14:13:48Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Comment from Adam Zey */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;When you begin a download and close the download manager, you can no longer track the progress of the downloads without having the window open and taking up space on the task bar. The biggest issue however is &amp;quot;Mum &amp;amp; Dad&amp;quot; users who think they&#039;ve cancelled their download when closing the download manager, and do not know how to get back to it other than clicking the link again (because there is no Dropbox button on the toolbar by default, and the menu is well hidden to the basic computer user). &lt;br /&gt;
&lt;br /&gt;
I would like to suggest a feasible idea for removing these issues. If you minimise or close the download manager, it could &amp;quot;minimize&amp;quot; into a statusbar block on the bottom right of the status bar that would contain the download icon and the text &amp;quot;15% of 3 Files...&amp;quot;. If the user clicks on the status bar block, the download manager maximizes out of the status bar. Therefore it is easy to keep an eye on downloads, beginners don&#039;t suffer &amp;quot;Where&#039;d it go!?&amp;quot; syndrome and the whole thing is easier to manage.&lt;br /&gt;
&lt;br /&gt;
== Comment from Alfred Kayser ==&lt;br /&gt;
Check out the &#039;Download Statusbar&#039; extension. This could serve as&lt;br /&gt;
a basis for the above &#039;simplified&#039; edition for the &#039;Mum&amp;amp;DadM&#039; case.&lt;br /&gt;
&lt;br /&gt;
== Comment from Ben Basson ==&lt;br /&gt;
The current download manager window pops up in front of the page the user is viewing. While this alerts the user to the new download, the window usually appears on top of useful content (with a similar annoyance factor to that of a popup advert) and has to be minimised.&lt;br /&gt;
&lt;br /&gt;
==== Reply by [[UseR:kroc|Kroc Camen]] ====&lt;br /&gt;
* Perhaps then have a tick box in the download manager for &amp;quot;AutoHide&amp;quot;. If ticked, the next time a download is fired, the statusbar block mentioned above would appear in the statusbar and flash once to show that it has appeared and something is downloading (like buttons on the taskbar flash to alert you to something). It&#039;s also no good if nothing appears and the user hasn&#039;t noticed the statusbar, so the flashing once would help.&lt;br /&gt;
&lt;br /&gt;
== Comment from Adam Zey ==&lt;br /&gt;
The current download manager window also does not pop up at all for short downloads. I&#039;ve been confused by this on occasion (Did my download start or not?), and I&#039;m an experienced user. &amp;quot;Mum &amp;amp; Dad&amp;quot; type users would likely be even more confused by this. (see [https://bugzilla.mozilla.org/show_bug.cgi?id=243324 Bug 243324])&lt;br /&gt;
&lt;br /&gt;
== Comment from BodziO ==&lt;br /&gt;
I think putting a little DM info on the statusbar is an excellent idea! I&#039;ve got also a proposition on my own. How about moving DM from a separate window to the sidebar. In my humble opinion it would be far better solution than the present one. Even key shortcut could remain unchanged. If you&#039;ve got enough space for your browser, you could still browse and check your downloads simultanousely. (sorry for my absolutely grammar and tense-trashing english :) )&lt;br /&gt;
&lt;br /&gt;
==== Reply by [[User:Kroc|Kroc Camen]] ====&lt;br /&gt;
*There is currently an extension for Firefox that allows you to have downloads in a sidebar, however this feature is not recommended for Mum&amp;amp;Dad users because internet-beginners have difficulty closing Sidepanes. This is evident from the number of times I&#039;ve seen people using IE and having their favourites sidepane on all the time because they don&#039;t know how to close it (stupid yes, but it&#039;s /*very*/ common!) Plus having a sidepane appear is rather jarring and scary since the whole page content might move all over the place due to smaller browser area.&lt;br /&gt;
&lt;br /&gt;
== Comment from apattison ==&lt;br /&gt;
Could I suggest the following:&lt;br /&gt;
&lt;br /&gt;
1. When closing the download manager using the close button on the window (or the window&#039;s menu), pop up a dialog telling the user that the downloads will not be stopped, only that the window will be closed. Only do this the first time they do this though. Also, give them the option to back out of performing this action using &amp;quot;yes/no&amp;quot; buttons on the window.&lt;br /&gt;
&lt;br /&gt;
2. Integrate the download manager into Firefox&#039;s main window. This would be more consistent with the idea of keeping everything in seperate tabs under a single window. If you go down this route then it would probably be useful to give folk the option of making the download manager a seperate window, via the existing prefs dialog.&lt;br /&gt;
&lt;br /&gt;
==== Reply by [[User:Kroc|Kroc Camen]] ====&lt;br /&gt;
# Additonal dialogs would piss-the-hell out of techies even if only once, and any additional unexpected dialogs are scary for new users. Note that many users may obstain from clicking the close button in the first place in fear that doing so may cancel their download. Telling them that this isn&#039;t the case &#039;&#039;&#039;After&#039;&#039;&#039; they&#039;ve sat and waited for the download to finish safely is just annoying. This whole matter could be simplified just by removing the close button on the Download Manager entirely and having just a minimize button (which turns into a close button, or a close button appears when all downloads are complete). This way the user will see the minimize button and know it won&#039;t close the window, but hide it out of the way.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
# I think there&#039;s an extension for putting downloads on another tab, my concern is that this takes up much screen space, can&#039;t be checked symultaneously to browsing and also breaks design principles - what about the back forward, reload and stop buttons on this new &amp;quot;tab&amp;quot; - they won&#039;t apply and therefore may confuse users as well as breaking many design principles in the process.&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Firefox:2.0_Multi-locale_Installers&amp;diff=5561</id>
		<title>Firefox:2.0 Multi-locale Installers</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Firefox:2.0_Multi-locale_Installers&amp;diff=5561"/>
		<updated>2005-04-23T14:08:54Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Comments User:Shishen */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Synopsis ==&lt;br /&gt;
When we ship the Firefox product currently, we can only fit one locale per installer which leads to duplicating the same binary code for multiple locales.  If we could fit more than one locale per installer, we could place ourselves in a much better situation where a 20-locale Firefox installer may be ~20 MB instead of 100 MB.  Since we ship 3 platforms, that takes our total size from 300 MB to 60 MB.&lt;br /&gt;
&lt;br /&gt;
This is the difference between shipping Firefox, Thunderbird, and Suite on the same CD, or having to split them up onto multiple CDs.&lt;br /&gt;
&lt;br /&gt;
=== Shishen&#039;s Comments ===&lt;br /&gt;
&lt;br /&gt;
Not only the installer should be multi-locale but the installed software too. Given Firefox runs on multi-users systems, each user might prefer to use Firefox in his own language.&lt;br /&gt;
&lt;br /&gt;
=== Caleb&#039;s Comments ===&lt;br /&gt;
&lt;br /&gt;
It would be great if the strings would be external, so if say, there&#039;s a minor security update coming up, users with locales other than en-US could apply the security fix without having to wait for a version of Firefox in their locale.&lt;br /&gt;
Since after all, incremental security updates are not allowed to change anything major in the interface, and even if they do, the patch could be applied in en-US first and when a language pack is available it will updated aswell.&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Firefox:2.0_Multi-locale_Installers&amp;diff=5538</id>
		<title>Firefox:2.0 Multi-locale Installers</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Firefox:2.0_Multi-locale_Installers&amp;diff=5538"/>
		<updated>2005-04-23T14:07:59Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Comments User:Caleb */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Synopsis ==&lt;br /&gt;
When we ship the Firefox product currently, we can only fit one locale per installer which leads to duplicating the same binary code for multiple locales.  If we could fit more than one locale per installer, we could place ourselves in a much better situation where a 20-locale Firefox installer may be ~20 MB instead of 100 MB.  Since we ship 3 platforms, that takes our total size from 300 MB to 60 MB.&lt;br /&gt;
&lt;br /&gt;
This is the difference between shipping Firefox, Thunderbird, and Suite on the same CD, or having to split them up onto multiple CDs.&lt;br /&gt;
&lt;br /&gt;
=== Comments [[User:Shishen]] ===&lt;br /&gt;
&lt;br /&gt;
Not only the installer should be multi-locale but the installed software too. Given Firefox runs on multi-users systems, each user might prefer to use Firefox in his own language.&lt;br /&gt;
&lt;br /&gt;
=== Caleb&#039;s Comments ===&lt;br /&gt;
&lt;br /&gt;
It would be great if the strings would be external, so if say, there&#039;s a minor security update coming up, users with locales other than en-US could apply the security fix without having to wait for a version of Firefox in their locale.&lt;br /&gt;
Since after all, incremental security updates are not allowed to change anything major in the interface, and even if they do, the patch could be applied in en-US first and when a language pack is available it will updated aswell.&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Firefox:2.0_Multi-locale_Installers&amp;diff=5537</id>
		<title>Firefox:2.0 Multi-locale Installers</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Firefox:2.0_Multi-locale_Installers&amp;diff=5537"/>
		<updated>2005-04-23T14:07:59Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* Comments User:Caleb */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Synopsis ==&lt;br /&gt;
When we ship the Firefox product currently, we can only fit one locale per installer which leads to duplicating the same binary code for multiple locales.  If we could fit more than one locale per installer, we could place ourselves in a much better situation where a 20-locale Firefox installer may be ~20 MB instead of 100 MB.  Since we ship 3 platforms, that takes our total size from 300 MB to 60 MB.&lt;br /&gt;
&lt;br /&gt;
This is the difference between shipping Firefox, Thunderbird, and Suite on the same CD, or having to split them up onto multiple CDs.&lt;br /&gt;
&lt;br /&gt;
=== Comments [[User:Shishen]] ===&lt;br /&gt;
&lt;br /&gt;
Not only the installer should be multi-locale but the installed software too. Given Firefox runs on multi-users systems, each user might prefer to use Firefox in his own language.&lt;br /&gt;
&lt;br /&gt;
=== Caleb&#039;s Comments ===&lt;br /&gt;
&lt;br /&gt;
It would be great if the strings would be external, so if say, there&#039;s a minor security update coming up, users with locales other than en-US could apply the security fix without having to wait for a version of Firefox in their locale.&lt;br /&gt;
Since after all, incremental security updates are not allowed to change anything major in the interface, and even if they do, the patch could be applied in en-US first and when a language pack is available it will updated aswell.&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Firefox:2.0_Multi-locale_Installers&amp;diff=5536</id>
		<title>Firefox:2.0 Multi-locale Installers</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Firefox:2.0_Multi-locale_Installers&amp;diff=5536"/>
		<updated>2005-04-23T14:07:22Z</updated>

		<summary type="html">&lt;p&gt;Caleb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Synopsis ==&lt;br /&gt;
When we ship the Firefox product currently, we can only fit one locale per installer which leads to duplicating the same binary code for multiple locales.  If we could fit more than one locale per installer, we could place ourselves in a much better situation where a 20-locale Firefox installer may be ~20 MB instead of 100 MB.  Since we ship 3 platforms, that takes our total size from 300 MB to 60 MB.&lt;br /&gt;
&lt;br /&gt;
This is the difference between shipping Firefox, Thunderbird, and Suite on the same CD, or having to split them up onto multiple CDs.&lt;br /&gt;
&lt;br /&gt;
=== Comments [[User:Shishen]] ===&lt;br /&gt;
&lt;br /&gt;
Not only the installer should be multi-locale but the installed software too. Given Firefox runs on multi-users systems, each user might prefer to use Firefox in his own language.&lt;br /&gt;
&lt;br /&gt;
=== Comments [[User:Caleb]] ===&lt;br /&gt;
&lt;br /&gt;
It would be great if the strings would be external, so if say, there&#039;s a minor security update coming up, users with locales other than en-US could apply the security fix without having to wait for a version of Firefox in their locale.&lt;br /&gt;
Since after all, incremental security updates are not allowed to change anything major in the interface, and even if they do, the patch could be applied in en-US first and when a language pack is available it will updated aswell.&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Mozilla2:ImageLib&amp;diff=6746</id>
		<title>Mozilla2:ImageLib</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Mozilla2:ImageLib&amp;diff=6746"/>
		<updated>2005-04-23T13:49:52Z</updated>

		<summary type="html">&lt;p&gt;Caleb: /* GIF */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Generally the image support of Mozilla should be aimed at:&lt;br /&gt;
* Supporting open standards: fully compliant and no proprietary extensions&lt;br /&gt;
* Optimized for image loading, decoding and displaying: one of the core requirements of an internet browser&lt;br /&gt;
* Minimal memory impact, allowing for small device support&lt;br /&gt;
== Encoding ==&lt;br /&gt;
Need to add APIs for encoding images.  See [[Mozilla2:Image_Encoding]].&lt;br /&gt;
== ColorSync ==&lt;br /&gt;
We should try to add Apple&#039;s ColorSync support to the image decoders on Mac and Windows. Many who work with digital media come across images with embedded color profiles and so the images look incorrect in Mozilla. Safari displays them correctly.&lt;br /&gt;
== JPEG2000 ==&lt;br /&gt;
JPEG2000: I have found an extension for mozilla and firefox that lets you view JPEG2000 pictures.  I&#039;ll post it for those you haven&#039;t found it yet, as long as the site&#039;s maninter can handle the extra traffic and those folks here are ok with a little adverstisement on this site.  It lead me to think that we should add the ability to view this file format in the standard dist, if it isn&#039;t much of a hassle.&lt;br /&gt;
&lt;br /&gt;
Isn&#039;t that illegal? JPEG2000 is heavily patented IIRC. Unless somebody&#039;s going to buy off the rights holders. And I didn&#039;t think mozilla.org had THAT sort of money. Anyway nobody uses JPEG2000, for this exact reason.&lt;br /&gt;
&lt;br /&gt;
Why not just read the [http://www.jpeg.org/faq.phtml?action=show_answer&amp;amp;question_id=q3f042a68b1081 JPEG2000 FAQ on patents] instead of FUD-ing?&lt;br /&gt;
== GIF ==&lt;br /&gt;
The current GIF handling can be further improved, by fixing current &#039;bugs&#039;: &lt;br /&gt;
* &amp;lt;s&amp;gt;Improve memory usage and performance of the decoder (see [https://bugzilla.mozilla.org/show_bug.cgi?id=274391 bug 274391]).&amp;lt;/s&amp;gt;&lt;br /&gt;
* Optimize memory usage for 8-bit (and less) images (see [https://bugzilla.mozilla.org/show_bug.cgi?id=143046 bug 143046]).&lt;br /&gt;
* Reduce source and object code size: Move GIF2.cpp into nsGIFDecoder2 (see  [https://bugzilla.mozilla.org/show_bug.cgi?id=196295 bug 196295])&lt;br /&gt;
These have all patches available awaiting reviews, requiring more priority than it currently has.&lt;br /&gt;
Additionally:&lt;br /&gt;
* Optimize for animated images. Currently all the frames are decoded, stored as 24-bit images, and all kept in the memory cache - this could be improved on by keeping the LZW compressed frames and only decode into 8-bit or 24-bit when required.&lt;br /&gt;
&lt;br /&gt;
== Video ==&lt;br /&gt;
The next step in animated images is full video support.&lt;br /&gt;
Is built in support for video formats a requirement for a browser?&lt;br /&gt;
* Most possibly no, it should be kept separate module to enable updates to support new formats not only with full browser update.&lt;br /&gt;
* Should there be support for video-specific tags? &amp;lt;tt&amp;gt;&amp;lt;img DynSrc=...&amp;lt;/tt&amp;gt;&lt;/div&gt;</summary>
		<author><name>Caleb</name></author>
	</entry>
</feed>