300137 - opening bookmark group fails if "When opening a bookmark group" is set to "Replace existing tabs"

Status: RESOLVED INVALID

(SeaMonkey :: Tabbed Browser, defect)

Description

[Manu]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050707 SeaMonkey/1.0a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050707 SeaMonkey/1.0a

This started occuring when I updated to the version of SeaMonkey I have
(Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050707
SeaMonkey/1.0a; Build ID: 2005070706, but I think you should be seeing that
anyway...) from a nightly build about a month or two old (can't say exactly
because I uninstalled it before installing SeaMonkey) of the Mozilla Application
Suite.

When I try to open a bookmark group with "When opening a bookmark group" set to
"Replace existing tabs" only the first tab in that bookmark group gets opened -
and to make things even weirder - in a new tab (in the background).
This can be reproduced with any number of tabs already open.
Added confusion is provided though, if only one tab is open and "Hide tab bar
when only one tab is open" is checked:
The first tab from the bookmark group is opened, but the tab-bar stays hidden
and the tab that was selected before trying to open the bookmark group keeps the
focus.
This results in the window looking as if nothing at all had happened.
The tab has however been opened, as it can be selected by the shortcuts
(Ctrl+Tab, Ctrl+Shift+Tab, Ctrl+PgUp, Ctrl+PgDwn), it displays in the tab bar,
if another tab is opened (either by clicking the bookmark group again, or by any
other method) (along with that new tab), and when closing the navigator window I
get a warning message telling me there are 2 tabs open.
This behaviour is very similar to some of that described in Bug 107276 (at least
by my first comment there and by Bug 113589, which has been marked as a
duplicate of 107276) and my guess would be that they share a common cause.

I wouldn't be surprised if both this bug and 107276 were symptoms of the same
bug, as they started happening at the same time for me and I guess this bug
could be caused by some component trying to close the first tab (to replace it
with a tab from the bookmark group), failing and stopping the whole operation.
The first tab from the group being opened would in some way sound logical, as
the coder might have decided to do that before closing the other tabs so the tab
bar doesn't disappear and reappear quickly, in case "Hide tab bar when only one
tab is open" is on. Opening all tabs before closing the currently open ones
would have taken too long most likely.
I would really recommend having a look at Bug 113589 (even if it's a bit long)
before trying to fix this one.

Reproducible: Always

Steps to Reproduce:
try to open a bookmark group with "When opening a bookmark group" set to
"Replace existing tabs"
Actual Results:  
only the first link from bookmark group opened

Expected Results:  
it should have opened all the links in the bookmark group

Comment 1

[Hermann Schwab]

wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b3) Gecko/20050708 SeaMonkey/1.0a

Setting as usual 'loading in the Background', changed from 'adding' to 'replace'
tested with buildID 2005070606:
had a tab, a group of four, and some other tabs open, and loaded that group
again from bookmarks. All tabs closed, 1st was loading first member of the group
(tinderbox), the other three were loading in the background in three tabs.

I closed Seamonkey, deleted the directory, unzipped the current nightly, and
loaded some tabs, read and deleted and loaded more. Then I loaded the group, and
got same behaviour: 1st tab loading and three more loading in the background.

'Replace tabs' replaced the 'Add tabs' behaviour with the patch from
Bug 203960 Make bookmark groups conditionally replace existing tabs instead of
appending
and instantly led to some still unfixed bugs, not seen in 'Add Tabs'.

Comment 2

[Manu]

i had conquery installed in my profile and that was the one causing the trouble...
still interesting this can happen...