Closed Bug 303943 Opened 19 years ago Closed 18 years ago

Resizing Bookmarks Manager Scrolls to the Top

Categories

(Core :: XUL, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 170045

People

(Reporter: whoselist, Assigned: jag+mozilla)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050807 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050807 Firefox/1.0+

This bug is similar to TB Bug 302516.

If the Bookmarks manager is restored down (i.e., is not maximized) and the list
of bookmarks exceeds the window height, resizing causes the Bookmarks Manager to
scroll to the top of the list.

Reproducible: Always

Steps to Reproduce:
1. Restore down the bookmarks manager
2. Scroll down through the bookmarks list
3. Resize the height of the window
Actual Results:  
Bookmarks list scrolls to the top

Expected Results:  
Scroll position does not change as window is resized
Confirmed.
I see this also in Mozilla1.7, so no (recent) regression
Assignee: nobody → jag
Status: UNCONFIRMED → NEW
Component: Bookmarks → XP Toolkit/Widgets
Ever confirmed: true
Product: Firefox → Core
QA Contact: bookmarks → jrgmorrison
Version: unspecified → Trunk
More precisely, it scrolls to make the selected item visible.
(In reply to comment #2)
>More precisely, it scrolls to make the selected item visible.
Which I understand is by design even when the selected item was already hidden.
The bookmark manager is *supposed* to scroll (vertically) when you resize it (horizontally)?  I find that hard to believe.
The comment from attachment 96245 [details] [diff] [review] to bug 163404 just says "make sure that the current selected item is still visible after the tree changes size." I don't see any attempt to determine the direction in which the tree changed size.
Dupe of bug 170045, no?  Or dependent thereon.
agree
Status: NEW → RESOLVED
Closed: 18 years ago
Depends on: 170045
Resolution: --- → DUPLICATE
No longer depends on: 170045
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.