918511 - Bookmark Open All in Tabs not working if many bookmarks are to open. The answer to the confirming dialog windows is ignored

Status: RESOLVED DUPLICATE of bug 1122697

(SeaMonkey :: General, defect)

Description

[AnyFile]

User Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Firefox/24.0 SeaMonkey/2.21 (Beta/Release)
Build ID: 20130916112303

Steps to reproduce:

Select a folder (or a subfolder) from the bookmark menu and select "Open All in Tabs"


Actual results:

If the folder contains a few number of items, the bookmarks are opened correctly.

If the folder contains many bookmarks (if I remember correctly more than 10 or more than 15), a dialog box appears asking or confirmation. The dialog box starts with "You are about to open 15 tabs. This might slow down ..."

The choice is between two buttons "Cancel"  ans "Open tabs"

If "Open tabs" is pressed no bookmarks is opened. The effect is the same as if cancel is pressed.


Expected results:

All of the bookmarks present in the folder should be opened, one in each tab

Comment 1

[Phoenix]

Can't reproduce this problem, all bookmarks opening just fine, check Safe Mode (Help - Restart with Add-ons Disabled)

Comment 2

[AnyFile]

I am afraid problem still present in Safe Mode

Comment 3

[Phoenix]

Next to try - clean profile (http://kb.mozillazine.org/Profile_Manager), don't move existing bookmarks to it, create new folder and test bookmarks set, and test with them

Comment 4

[AnyFile]

Still not working in a new profile (I used both an already created profile under a different user and a fresh new created profile).

Comment 5

[therube]

Anything relevant show up in Error Console when this happens?

In addition to disabling Extensions, does the problem persist if you also disable all Plugins?

Comment 6

[AnyFile]

Nothing shows up in the terminal from which I started the program.

I have tried to disable all the Extensions and plugins, with no results.

I looked up in Tools -> Web Development -> Error Console (I hope this was what you were referring to) I found that when the problem happens a new line is written

Timestamp: 30/09/2013 18:43:45
Error: TypeError: focusManager.activeWindow is null
Source File: resource://gre/modules/PlacesUIUtils.jsm
Line: 614

Comment 7

[Iacopo Benesperi [:iacchi]]

I can confirm this bug on SeaMonkey 2.22, Linux x64, with both an used and a clean profile created just for this test. This is the error shown on console:

Date and time: 02/11/2013 15:05:54
Error: TypeError: focusManager.activeWindow is null
Source file: resource://gre/modules/PlacesUIUtils.jsm
Line: 614

Comment 8

[Phoenix]

/*Suddenly wakes up*/
Introduced by Bug 899104

Comment 9

[[e-mail]]

Probably only happens on Linux because it's easier to track focus on the other OSes and so we know where focus is after the prompt.

Comment 10

[[e-mail]]

There is a case where the previous code (i.e. before Private Browsing) might not work properly on Linux; I don't know whether anyone is in a position to check.

Steps to reproduce:

Open the Bookmarks manager
Close all browser windows
Right-click a folder with at least 15 items
Select "Open All in Tabs"

Comment 11

[Iacopo Benesperi [:iacchi]]

I can download a previous version and try, but I don't remember which  version should I download exactly (i.e. before private browsing). Can you tell me?

Comment 12

[therube]

http://www.seamonkey-project.org/releases/seamonkey2.18/#new

2.18 says:
Basic Private Browsing support has been added (experimental for now).

So suppose 2.17 would be good to work with.
http://www.seamonkey-project.org/releases/2.17

Comment 13

[Iacopo Benesperi [:iacchi]]

Sorry for being so late. I tried with v. 2.16 and the bug is not there.

Comment 14

[AnyFile]

Work for me now (version 2.26, I do not know if in recent previous versions it was working or not)

Comment 15

[AnyFile]

Sorry, actually still not working

Comment 16

[Iceberg]

I confirm this bug on Linux.
This bug is present from version 2.21 up to the current 2.30.
It is not present in any Windows version.
I do not know the behavior of the Mac OS version.

Comment 17

[AnyFile]

It seems the problems was solved, at least for me, passing from version 2.32 to version 2.32.1.

Thank you to everybody involved.