Bug 89225 - opening link in new tab or window should copy / preserve back/forward history
Summary: opening link in new tab or window should copy / preserve back/forward history
Status: CONFIRMED
Alias: None
Product: konqueror
Classification: Applications
Component: tabbing (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 109801 191130 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-09-10 11:29 UTC by Clarence Dang
Modified: 2010-04-21 14:20 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Clarence Dang 2004-09-10 11:29:41 UTC
Version:            (using KDE KDE 3.3.0)
Installed from:    Compiled From Sources

e.g.:

1. Go to http://bugs.kde.org/
2. Click "The most hated bugs"
3. Middle mouse click on any hated bug to open it in a new tab.  The new tab has no history.  It should have http://bugs.kde.org/ and "The most hated bugs" as the history.

This is useful e.g. for google searches.  I middle mouse click on a bunch of hits to open them in new tabs.  When I'm looking at hit and realise that it's useless, I want to be able to press Back to return to the google search results (I may not have the original google search results tab open).
Comment 1 Daniel Teske 2005-07-28 22:29:59 UTC
*** Bug 109801 has been marked as a duplicate of this bug. ***
Comment 2 David Faure 2008-04-02 23:46:06 UTC
IIRC Eduardo wants to implement this
Comment 3 Eduardo Robles Elvira 2008-04-02 23:50:20 UTC
yeah, that's something that goes to me TODO list ;) It's quite trivial, so we'll hopefully have it for 4.1/trunk soon enough
Comment 4 Angel Blue01 2009-03-04 22:02:40 UTC
The fact that new window/tab DON'T preserve their parent's history is one of the problems in every browser. Is there any work being done on this bug?
Comment 5 Frank Reininghaus 2010-04-21 14:20:41 UTC
*** Bug 191130 has been marked as a duplicate of this bug. ***