227125 - 'forward' broken if a group of tabs (groupmark) replaces about:blank

Status: RESOLVED EXPIRED

(SeaMonkey :: Tabbed Browser, defect)

Description

[Eric Lawrence]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6b) Gecko/20031130
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6b) Gecko/20031130

This got lost in the noise of bug 203960, so I figured I'd file a new bug.

If a groupmark is opened in a blank window in 'replace' mode, then hitting the
back button works: it takes you back to the blank window.  However, now the
forward button is grayed out, so you can't get back to your group of tabs. 
Also, this shows up in the JS console:

Error: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIWebNavigation.gotoIndex]"  nsresult:
"0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame ::
chrome://global/content/bindings/tabbrowser.xml :: refresh :: line 349"  data: no] 


Reproducible: Always

Steps to Reproduce:

Comment 1

[Frankie]

Eric, does this still happen in a 1.7.x build? I am unable to replicate your bug
using Firefox, but it may have different defaults.

Comment 2

[Eric Lawrence]

I just tried this in Mozilla 1.7.x and the back/forward behavior now works for me.

As for the javascript error, if I start with two or more blank tabs, and open a
groupmark on top of them, then it comes up in the console.  It does not come up
if I start with just a single blank tab.  The back/forward buttons still work.

Firefox seems to deal with groupmarks differently.  Each tab has its own
individual history list, so this bug would not apply to Firefox.

Comment 3

[Eric Lawrence]

oops, I meant Mozilla 1.7.5 above.

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.