Closed
Bug 196554
Opened 23 years ago
Closed 23 years ago
Bookmark toolbar menus behave strangely
Categories
(Camino Graveyard :: Toolbars & Menus, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: visa, Assigned: Brade)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4a) Gecko/20030308 Chimera/0.7+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4a) Gecko/20030308 Chimera/0.7+
In build 2003030808, bookmark toolbar menus open in a different way than previously.
1. Folders used to open under the cursor so that you were able to click the
first bookmark without moving your mouse. Now they open below the folder. I
would prefer the old behavior.
2. You can't open another folder with a single click anymore if you have another
folder open. You have to first click somewhere to close the currently opened
folder and only then you can open another folder. Also, double-clicking another
folder closes and re-opens the first folder, instead of opening the folder you
were clicking.
Reproducible: Always
Steps to Reproduce:
1. Click one of the folders in your bookmark toolbar to open the folder. Let's
call this "folder A"
2. Double-click another folder ("folder B").
Actual Results:
Folder A was closed and re-opened.
Expected Results:
Folder A should've been closed and folder B opened.
OK, I have to take my words back... I reverted to build 2003030613 and noticed
that folders don't actually open directly under to mouse cursor. However, they
do open closer the cursor than in build 2003030808. Also, you can't open a
folder by just clicking it if there's another folder open. Double-clicking
closes the previous folder and doesn't open or re-open any folder.
Comment 2•23 years ago
|
||
nothing looks awkward in Camino 2003051604 on my end.
Visa, is this still an issue for you and if so can you provide a screenshot of
the problem?
No, it was fixed soon afterwards. I wonder why nobody closed this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•