Closed
Bug 184650
Opened 23 years ago
Closed 20 years ago
Bookmarks not highlighting when moving from a folder
Categories
(SeaMonkey :: Bookmarks & History, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: garsh, Assigned: bugs)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021206
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021206
linux x86 2002-12-06-05
After left-clicking on the "Bookmarks" entry in the menu bar, I
highlight one of my bookmark folders.
If I then move the mouse to an adjacent entry (up or down), the new
entry will sometimes NOT get highlighted.
There is some timing involved here. You have to move the mouse
pointer to the new entry and then stop moving the mouse BEFORE the
display of the previous bookmark folder's contents disappears.
Reproducible: Sometimes
Steps to Reproduce:
See above
Actual Results:
bookmark entry is not highlighted.
If the new entry is a folder, the folder contents are also
not displayed.
Expected Results:
Entry should always be highlighted.
Comment 1•21 years ago
|
||
unable to reproduce with Mozilla 1.7 beta.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 2•21 years ago
|
||
I can still reproduce this quite easily with the latest nightly build.
Mozilla 1.7b
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040323
Build ID: 2004032308
Given the timing involved, it is probably easier to reproduce this on an older
machine. I can easily reproduce this on a P-3 500MHz machine running Red Hat 9
Linux. I just highlight a bookmark item, then quickly tap the mouse up or
down. Usually, the entry that it lands on will not get highlighted.
I also have a Centrino 1.3GHz machine running windows, and I am completely
unable to reproduce the problem there. So please try to reproduce on an older
machine.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 3•20 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 4•20 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago → 20 years ago
Resolution: --- → EXPIRED
I have same problem with Firefox 1.5.0.1 (Windows XP. View, Go, partially Bookmarks (all under Firefox and Mozilla Information folder) and partially Tools menu (Adblock Plus and DownThemAll menu items) seems to be affected. Highlight blinks when you move cursor otherwise it is not shown at all, folders are not opened. Restarting Firefox corrects problem for a while.
This maybe related to memory usage, because it seems to show up when Firefox uses more than 50MB of memory and sometimes it disappears when memory usage goes down. I noticed this first time in 1.5 and it is not solved in 1.5.0.1.
You need to log in
before you can comment on or make changes to this bug.
Description
•