2
edits
Talk:Firefox:3.0 Tabbed Browsing: Difference between revisions
Jump to navigation
Jump to search
Talk:Firefox:3.0 Tabbed Browsing (view source)
Revision as of 11:04, 5 September 2007
, 5 September 2007→Why not use the back button?
(Adding features and various scenarious of grouped (hierarchical) tab browsing) |
|||
| Line 37: | Line 37: | ||
* No, bad idea. A back button is for "going back", having it close a tab is counter-intutive: "Where'd my tab go?" Further, you lose your "forward" history at that point, from either the new tab or the old one (depending on implementation). A new tab is a branch in your browsing, separated from the original tab; the two need to navigate separately. Instead of trying to merge back into the original tab, just duplicate the old back list in the new tab, adding the page you were on. That way, clicking back does exactly what you'd expect: takes you back to where you reached that page from, but without making the tab disappear. As Kroc mentioned above, this is a place where IE got it right... or at least closer than Firefox has. Opening a new tab by hand (e.g. File-New Tab) should still be a fresh start, but tabs opened via links should borrow the setting of the page that spawned them, as if they'd been duplicated, then had the link clicked. [All of this applies to windows too, but tab/window is just too cumbersome.] -[[User:FunnyMan3595|FunnyMan3595]] 19:15, 14 Aug 2005 (PDT) | * No, bad idea. A back button is for "going back", having it close a tab is counter-intutive: "Where'd my tab go?" Further, you lose your "forward" history at that point, from either the new tab or the old one (depending on implementation). A new tab is a branch in your browsing, separated from the original tab; the two need to navigate separately. Instead of trying to merge back into the original tab, just duplicate the old back list in the new tab, adding the page you were on. That way, clicking back does exactly what you'd expect: takes you back to where you reached that page from, but without making the tab disappear. As Kroc mentioned above, this is a place where IE got it right... or at least closer than Firefox has. Opening a new tab by hand (e.g. File-New Tab) should still be a fresh start, but tabs opened via links should borrow the setting of the page that spawned them, as if they'd been duplicated, then had the link clicked. [All of this applies to windows too, but tab/window is just too cumbersome.] -[[User:FunnyMan3595|FunnyMan3595]] 19:15, 14 Aug 2005 (PDT) | ||
* I agree with FunnyMan3595. Simply copy the history when the new tab is opened when you click on a link (eg the case where webmaster assign the link to be opened in new window, and Firefox changes it to open new tab instead). | |||
However no history should be copied for the following situations: | |||
- you deliberately want to open in a new tab (eg you middle click on the link to open in a new tab). If you don't want to load it in current tab, you most likely don't want history either. | |||
- You press Ctrl+T to open a new tab | |||
Even better, make all options so users can configure in what situations should the history be copied. --[[User:Wai Wai|Wai]] 04:04, 5 September 2007 (PDT) | |||
== Complex Solution == | == Complex Solution == | ||