237259 - Collapsing folders toward bottom of Bookmarks in Sidebar causes currently selected bookmark to load

Status: RESOLVED WORKSFORME

(SeaMonkey :: Sidebar, defect)

Description

[Travis Evans]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6) Gecko/20040113

If a bookmark in the Sidebar is highlighted (selected) and then an expanded
Bookmarks folder is collapsed toward the bottom, so that the Sidebar's scroll
jumps back up to prevent empty space at the bottom of the Sidebar, the last
highlighted bookmark is loaded even though it was not clicked.

Reproducible: Always
Steps to Reproduce:
1. Open the Sidebar and switch to the Bookmarks tab.
2. Click a bookmark to open it.
3. In the same window/tab the bookmark was opened in, open a different
webpage/document without using the Sidebar.
4. Without highlighting another folder or bookmark in the Sidebar, scroll the
Sidebar to the very bottom.
5. Find a folder near the bottom of the list and open it, WITHOUT highlighting
it (read: only click the arrow/plus sign to the left). It is necessary to open a
folder that contains enough bookmarks or other folders so that you can scroll
down some more.
6. Again, scroll down the list all the way, without highlighting any other
bookmarks. (Up to this point, the bookmark selected in Step 2 should have still
been highlighted this whole time.)
7. Collapse the folder just opened the same way, clicking the arrow/plus sign
without highlighting it.
Actual Results:  
When the Sidebar scroll jumps back up on collapsing the folder, the bookmark
highlighted in Step 2 automatically loads in the current tab/window, even though
it wasn't clicked, and even if the mouse cursor wasn't anywhere near that
bookmark's entry. 

Expected Results:  
Since the bookmark wasn't clicked, it should not be loaded when the Sidebar
window jumps back.

Comment 1

[Travis Evans]

Changed summary (I originally wrote "...causes last selected bookmark..." but it
should more accurately be "...causes currently selected bookmark..."

Comment 2

[Martin Heller]

Mozilla/5.0 (Windows; U; Win98; rv:1.7.3) Gecko/20040913 Firefox/0.10.1

Confirmed for Firefox 1.0PR. And Fx0.9.x and 0.8.

It happens when closing (collapsing) folders and as well when expanding them.
I start Fx, default theme, safe-mode, with a large bookmark sidebar as seen on
the first screenshot http://www.hallofreun.de/temp/before.png
click a bookmark, e.g. "heise online"
Move the marking color down with the arrow key to "NFL.com"
click the small + before Foren (third folder from above)
http://www.hallofreun.de/temp/after.png
A scrollbar occurs, folder "Foren" expands, (good)
the start of folder "Foren" moves up        (bad)
bookmark "NFL.com" loads                    (ugly).

Comment 3

[Martin Creutziger [:MMx]]

Looks like this bug really exists. Please test it also with a current *trunk*
nightly so that we can figure out if the problem exists outside the AVIARY-branch.

Comment 4

[Martin Heller]

Not with a nightly but just reproduced it under Linux:
Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914 Firefox/0.10
Both, the collapsing and the expanding version.

Comment 5

[Martin Heller]

Confirmed for Firefox 1.0RC1
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.3) Gecko/20041020 Firefox/1.0

Comment 6

[Gary Cauthon]

I've noticed that the bug is triggered by the distance between the expanded
folder and the previously selected bookmark.  If both can appear on the screen
at once, then the bug is not triggered.  IOW, the folder is expanded and the
previously selected bookmark is not opened.  If the expanded folder has so many
bookmarks that the folder name is scrolled off the screen, then the previous
bookmark is opened.  Also, the bug never occurs when right clicking on the
folder and choosing expand/collapse.

Comment 7

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 8

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420

Comment 10

[Karsten Düsterloh]

WFM using Windows XP/SM 2.8a1 and Linux/trunk.