Comment #2 on issue 1639 by rablaridash: New tab do not inherit parent  
history
http://code.google.com/p/chromium/issues/detail?id=1639

This functionality can be currently achieved by right-clicking on a tab,  
selecting
"duplicate", then clicking the link in the duplicated tab. This is a bit  
more
cumbersome than right-clicking on the link and selecting "open link in new  
tab",
middle-clicking on the link. It appears that users intuitively expect  
opening a link
in a new tab to have this same behavior, however.

I believe it is done the way it is because of tradition, and because of  
performance.
Tradition is only a concern when it governs user expectations, which does  
not appear
to be a factor in this case. Performance, however, is. Duplicating a tab is  
generally
more resource-intensive than creating a fresh one. There are ways to reduce  
the
performance hit, however.

Perhaps a quicker path to the desired functionality could be added, such as  
a new
option on the right-click menu ("Open link in duplicated tab"), or a  
checkbox in
Options to make this the default middle-click behavior (with a warning  
about the
performance hit)?

I haven't looked at how Chrome stores History, but it obviously has a global
component because the browser maintains global history across all tabs. A  
tree
structure of the current history across related tabs could be maintained so  
that they
could access the same history list without needing to duplicate it, thus  
reducing the
resource cost of duplicating a tab. Chrome may already do it this way, and  
I just
don't know it.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to