3
edits
Talk:Firefox:3.0 Tabbed Browsing: Difference between revisions
Adding link to Firefox Workspaces RFE.
m (→Why not use the back button?: edit my post) |
(Adding link to Firefox Workspaces RFE.) |
||
| Line 157: | Line 157: | ||
* Allow custom tab groups, so even that you have a few pages from the same website open, you can have them in different groups. | * Allow custom tab groups, so even that you have a few pages from the same website open, you can have them in different groups. | ||
=== Users' Comments === | === Users' Comments === | ||
'''Nested Grouping''' | |||
Each tab group should | :Each tab group should be able to hold two kinds of objects | ||
* | *A Tab | ||
*A Tab group | |||
(The tab groups can be considered akin to folders in a file system and Tabs as file objects). | |||
Each tab group should essentially remember, among other things, the last object of focus - which can be either a tab or tab group. The last object of focus should be focussed when the tab group if focussed. | |||
*One of the main concerns of the tab groups in general is the excessive use of memory. This should be avoided at any cost to prevent dampening user experience. One way is by having to fetch URLs in a group only when they are focussed. So the hierarchical tab group acts like kind of (horizontal) bookmark folder with extended functionality.(Sort of like thumb nail views of objects of a folder in a file browser) | |||
* | **Users with lots of memory and bandwidth or with limited number of URLs opened should be able to disable this option, so that all pages in all groups are fetched and loaded in memory. | ||
* The | **We can have user preferences to enable background pre-fetching. The depth of pre-fetching could be user configurable defaulting to depth of 1 (consisting only of tabs under a group). A depth level of 2 would additionally include the tabs in the tab groups at depth 1. A depth of 3 would additionally include the tabs in the tab groups at depth 2. So on.. and so forth.. | ||
'''Typical use case scenario''' | |||
* | *On Installing the extension a default group is created and all previously opened URLs if any are moved into that group. | ||
* | *The address input bar now has a companion drop down list located adjacent to it containing the list of tab groups. The selected group in the drop down list reflects the currently focussed group. Changing the group changes the selected item in the drop down list and vice versa. Any URL that is typed into the address bar will be opened into the group selected in the drop down list. | ||
** | **The binding between the drop down list and group focussing should be user customisable allowing the user to disable either of the two way connection. | ||
* | *The drop down list may be by default hidden to conserve ui space and be represented by a user clickable icon which then expands into the full view of the drop down list and contracts back once focus is lost. | ||
** This behaviour should be user configurable with user pref: | *Tabs should be draggable from one group to another. | ||
When a duplicate URL that is opened in another group is opened - Focus on the existing tab (default)/open a duplicate. | |||
**Whether the Tab is moved or copied into the target group should be user customisable defaulting to Move. | |||
*By default, Tabs in multiple groups, representing the same URL, should be pointers to the same rendered page, if it is technically feasible. And user should be notified when he opens a duplicate URL by echoing a non-obstructive message in some part of the UI like 'This URL is already open in <group>. Do you want to switch to it? (yes/no)' | |||
**This behaviour should be user configurable with user pref: | |||
When a duplicate URL that is opened in another group is opened - Focus on the existing tab (default)/open a duplicate. | |||
**This might turn out to be feature to enable to user to switch swiftly from one group to another. Wherein, the user types the URL that is already opened in a group (that he may or may not remember) and he is taken to the existing group. | |||
--[[User:Mohanr|Mohanr]] 23:16, 28 July 2007 (PDT) | |||
---- | ---- | ||
:Grouping of tabs in order to create some hierarchy of currently visited web sites would be nice. Right now, I have opened 15 tabs and I must search linearly for a certain tab, which reduces efficiency of my work. And this is how I would love to use it: | :Grouping of tabs in order to create some hierarchy of currently visited web sites would be nice. Right now, I have opened 15 tabs and I must search linearly for a certain tab, which reduces efficiency of my work. And this is how I would love to use it: | ||
:*Ideally, there would be a root group if the user doesn't specify anything. If the user chooses to open a new link, he should be presented with the option to open the link in a new tab in a new group. It should be possible to change the name of the group afterwards. | :*Ideally, there would be a root group if the user doesn't specify anything. If the user chooses to open a new link, he should be presented with the option to open the link in a new tab in a new group. It should be possible to change the name of the group afterwards. | ||
:*There is exactly one group that is currently active. Other groups that are available should be presented by a special tab. | :*There is exactly one group that is currently active. Other groups that are available should be presented by a special tab. | ||
:*To change the group context, the user clicks on the special group tab. This means, the previous group becomes inactive and the tabs of this group collapse to the special group tab. The group tab of the now active group expands to the tabs of the web sites it represents. | :*To change the group context, the user clicks on the special group tab. This means, the previous group becomes inactive and the tabs of this group collapse to the special group tab. The group tab of the now active group expands to the tabs of the web sites it represents. | ||
:If I had knowledge and/or time, I would implement that as an extension, but I hope this short description helps to gain some ideas of how the user (at least me) would like to expirience grouped tabbed browsing. [[User:Lukrez|Lukrez]] 01:41, 17 Mar 2006 (PST) | :If I had knowledge and/or time, I would implement that as an extension, but I hope this short description helps to gain some ideas of how the user (at least me) would like to expirience grouped tabbed browsing. [[User:Lukrez|Lukrez]] 01:41, 17 Mar 2006 (PST) | ||
:If different tab coloring is used, it should definitely be themed and/or customizable. The bright colors you've proposed would look terrible on a black-and-white theme like BlackJapan, for example. Also, with tab groups, i think it should be possible to use two bars: one for tab groups, and another for tabs within currently selected group. This could be used as an alternative for multi-window browsing, too (some users, i.e. me use separate windows to group tabs). However, i'm not sure if it should be on by default, as it could confuse some users. and possibly add clutter.--[[User:Nublet|Nublet]] 08:34, 24 August 2006 (PDT) | :If different tab coloring is used, it should definitely be themed and/or customizable. The bright colors you've proposed would look terrible on a black-and-white theme like BlackJapan, for example. Also, with tab groups, i think it should be possible to use two bars: one for tab groups, and another for tabs within currently selected group. This could be used as an alternative for multi-window browsing, too (some users, i.e. me use separate windows to group tabs). However, i'm not sure if it should be on by default, as it could confuse some users. and possibly add clutter.--[[User:Nublet|Nublet]] 08:34, 24 August 2006 (PDT) | ||
* And here... | *And here... | ||
*** I want the option to disable tabbed browsing entirely. | ***I want the option to disable tabbed browsing entirely. | ||
*** I want the option to disable target="_blank" tag entries | ***I want the option to disable target="_blank" tag entries | ||
*** I want the back button to be enabled for new windows (when *I* choose to open them) from a context menu window open and the new window should retain the history state of the "parent" window. | ***I want the back button to be enabled for new windows (when *I* choose to open them) from a context menu window open and the new window should retain the history state of the "parent" window. | ||
*** I want the browser to NEVER resuse existing windows to open shortcuts - this is EXTREMELY annoying. | ***I want the browser to NEVER resuse existing windows to open shortcuts - this is EXTREMELY annoying. | ||
*** I want to have COMPLETE control over my browsing experience, no matter what some web publishing lacky thought would be a good idea. | ***I want to have COMPLETE control over my browsing experience, no matter what some web publishing lacky thought would be a good idea. | ||
:If different tab coloring is used, it should definitely be themed and/or customizable. The bright colors you've proposed would look terrible on a black-and-white theme like BlackJapan, for example. Also, with tab groups, i think it should be possible to use two bars: one for tab groups, and another for tabs within currently selected group. This could be used as an alternative for multi-window browsing, too (some users, i.e. me use separate windows to group tabs). However, i'm not sure if it should be on by default, as it could confuse some users. and possibly add clutter.--[[User:Nublet|Nublet]] 08:34, 24 August 2006 (PDT) | :If different tab coloring is used, it should definitely be themed and/or customizable. The bright colors you've proposed would look terrible on a black-and-white theme like BlackJapan, for example. Also, with tab groups, i think it should be possible to use two bars: one for tab groups, and another for tabs within currently selected group. This could be used as an alternative for multi-window browsing, too (some users, i.e. me use separate windows to group tabs). However, i'm not sure if it should be on by default, as it could confuse some users. and possibly add clutter.--[[User:Nublet|Nublet]] 08:34, 24 August 2006 (PDT) | ||
I would have no groups by default and allow tabs to be dragged onto each other to create a stack effect. | I would have no groups by default and allow tabs to be dragged onto each other to create a stack effect. This could then be navigated via a dropdown arrow on the right (or left) of the tab itself. The TabStack/TabGroup could then be renamed and saved as bookmark list Bookmark lists could be hydrated as TabStack/TabGroup from the bookmarks menu or through some other means. | ||
This could then be navigated via a dropdown arrow on the right (or left) of the tab itself. | |||
The TabStack/TabGroup could then be renamed and saved as bookmark list | |||
Bookmark lists could be hydrated as TabStack/TabGroup from the bookmarks menu or through some other means. | |||
For me the important thing is the level of control. | For me the important thing is the level of control. | ||
Algorythms could be introduced to allow Firefox to second guess what groups I might choose to create but in truth I think I would want groups according to research topic and I doubt we could ever get FF to read my mind like that. | Algorythms could be introduced to allow Firefox to second guess what groups I might choose to create but in truth I think I would want groups according to research topic and I doubt we could ever get FF to read my mind like that. [[User:RoryBecker|RoryBecker]] 02:23, 13 October 2006 (PDT) | ||
[[User:RoryBecker|RoryBecker]] 02:23, 13 October 2006 (PDT) | |||
:For me, the most useful feature would be if tabs were grouped in a tree-like fashion, e.g. by a small vertical offset for "children tabs". So if I open a new tab B from a link in tab A, B should be opened directly right of A (instead of rightmost, it's much more intuitive and should be done by default even without tab grouping) and some pixels lower so I can see that it's A's child. Or have tab A include B visually. Tabs opened from bookmarks/addressbar/search are placed rightmost at root level but can be dragged into another branch.--[[User:Bugmenot|Bugmenot]] 15:09, 25 October 2006 (PDT) | :For me, the most useful feature would be if tabs were grouped in a tree-like fashion, e.g. by a small vertical offset for "children tabs". So if I open a new tab B from a link in tab A, B should be opened directly right of A (instead of rightmost, it's much more intuitive and should be done by default even without tab grouping) and some pixels lower so I can see that it's A's child. Or have tab A include B visually. Tabs opened from bookmarks/addressbar/search are placed rightmost at root level but can be dragged into another branch.--[[User:Bugmenot|Bugmenot]] 15:09, 25 October 2006 (PDT) | ||
<br> | |||
---- | ---- | ||
| Line 231: | Line 233: | ||
Yep, it would be really great to have tab grouping which could be similar to the feature in excel when grouping columns or rows, you can have several levels of grouping just as you would see fit. for example you could create one level which would be for example OS: and under that additional groups such as Linux, windows, solaris and then again another subgroup in accordance to requirement, networking, administrating, registry hacks etc. | Yep, it would be really great to have tab grouping which could be similar to the feature in excel when grouping columns or rows, you can have several levels of grouping just as you would see fit. for example you could create one level which would be for example OS: and under that additional groups such as Linux, windows, solaris and then again another subgroup in accordance to requirement, networking, administrating, registry hacks etc. | ||
each day ive got at least 15 different tabs covering different topics and tend to keep them open for quick refference and review, grouping could make my work much easier. in addition to tab grouping, tab grouping history with urls could be saved just as history sidebar where you could go back in time and retrieve the "view" that you had back then, that would make retrieval from history much simpler and more straight forward from the tab grouping topic perspective. | each day ive got at least 15 different tabs covering different topics and tend to keep them open for quick refference and review, grouping could make my work much easier. in addition to tab grouping, tab grouping history with urls could be saved just as history sidebar where you could go back in time and retrieve the "view" that you had back then, that would make retrieval from history much simpler and more straight forward from the tab grouping topic perspective. to the likes of others, i would "create the extension" if i knew hot to program :/ ofcourse this could be implimented on all firefox versions :D -RutePoint- | ||
to the likes of others, i would "create the extension" if i knew hot to program :/ ofcourse this could be implimented on all firefox versions :D | |||
-RutePoint- | |||
---- | ---- | ||
<br> This is the BIG THING that is still missing the ONE feature that would help a lot of professionals and regular users... | |||
I also have a few ideas that i posted in the URL: | |||
[http://m.domaindlx.com/tabgrouper/ Tab Grouper] | |||
--[[User:Jonh tomas|Jonh tomas]] 15:39, 17 November 2006 (PST) | |||
<br> | |||
-- | ---- | ||
See: {{bug|505214}} ("Implement Workspaces"). | |||
:[[User:Darkangel|Darkangel]] 20:46, 20 July 2009 (UTC) | |||
---- | ---- | ||