Bug 3546

Summary: Can't go back after first link followed from a new window opened by gmail
Product: WebKit Reporter: Stuart Morgan <stuartmorgan>
Component: HistoryAssignee: Brady Eidson <beidson>
Status: RESOLVED FIXED    
Severity: Normal CC: ddkilzer, occupant4
Priority: P2 Keywords: GoogleBug, InRadar
Version: 412   
Hardware: Mac   
OS: OS X 10.4   

Description Stuart Morgan 2005-06-15 09:58:38 PDT
* SUMMARY
If you click an external link in a gmail message, then navigate to another page
in the new window (using bookmarks, following a link, typing a url, etc.), the
page that was originally opened can't be returned to with the back button (the
button is disabled, and if you browse further the window/tab history on the back
button will never show it).  It doesn't even show up in the global history,
either the menu or the listing in the bookmark manager.

* STEPS TO REPRODUCE
1. Open a gmail email with a link in it
2. Click the link
3. Navigate to another page in the new window
4. Try to get back to the previous page through any means

* RESULTS
Page is mysteriously missing from history.

* REGRESSION
Also broken in 10.3.9; haven't tried regressing further back

Apple Bug: rdar://4147975
Comment 1 David Kilzer (:ddkilzer) 2006-07-12 21:57:39 PDT
Reassigning to webkit-unassigned for more exposure.

Comment 2 David Kilzer (:ddkilzer) 2006-07-12 21:58:16 PDT
GMail is Google.

Comment 3 Brady Eidson 2007-01-05 13:44:11 PST
"rediscovered" this bug while exploring + fixing http://bugs.webkit.org/show_bug.cgi?id=12117
I need to take a more seriously look at it now!!
Comment 4 Brady Eidson 2007-01-05 13:49:53 PST
Confirmed nothing "bad" happens in a release build other than the opened link getting left out of global and back/forward history.  That noted, it may be a little while before I get to this one.
Comment 5 Brady Eidson 2007-04-11 11:39:17 PDT
<rdar://problem/4664154>
Comment 6 Brady Eidson 2007-04-13 13:47:25 PDT
Fixed landed in r20878
Comment 7 David Kilzer (:ddkilzer) 2007-04-19 05:32:54 PDT
*** Bug 13122 has been marked as a duplicate of this bug. ***