Closed Bug 237738 Opened 21 years ago Closed 19 years ago

Dragging link to bookmarks sub-folder causes sub-folder to remain on screen.

Categories

(SeaMonkey :: Bookmarks & History, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: jhchan, Assigned: p_ch)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 MultiZilla/1.6.0.0a Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 MultiZilla/1.6.0.0a When dragging a link to the bookmarks into a sub-folder causes that bookmark sub-folder to stay open on the screen until a previously saved bookmark (or the newly added one) is clicked on. The bookmark sub-folder stays open as if you were looking at it. The folder should normally disappear if you click elsewhere on the screen. This is not new to release 1.6 and also happens with standalone mozilla (no plugins or addins like multizilla installed). This has happened in past releases as well, 1.4 and 1.5 as far as I can remember using. Reproducible: Always Steps to Reproduce: 1. Drag a link to the bookmarks menu into a sub-folder 2. Drop it in the desired sub-folder. 3. The location you dropped the link now stays open on the screen even if you click elsewhere. Actual Results: Bug reproduced. Bookmark folder stays open until a previously saved bookmark is clicked on. Expected Results: Bookmark folder should close when mouse is moved off the menu and user clicks elsewhere on the screen. This happens with default theme as well as others.
similar: bug 211891
Blocks: 133604
Summary: Dragging link to bookmarks sub-folder casues sub-folder to remain on screen. → Dragging link to bookmarks sub-folder causes sub-folder to remain on screen.
Product: Browser → Seamonkey
*** Bug 211891 has been marked as a duplicate of this bug. ***
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/
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: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.