Closed Bug 160082 Opened 22 years ago Closed 14 years ago

Pulldown sub-menu remains on screen

Categories

(SeaMonkey :: Bookmarks & History, defect)

x86
All
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: ej0c, Unassigned)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.1b) Gecko/20020722
BuildID:    2002072204

I just finished installing this build on this machine, checked my
mail via the web mail client for corecomm, and wiched to set the web mail page
as a personal toolbar item.

Clicked on Bookmarks, then "Bookmark this page". It did. 

Then clicked Bookmarks again, selected the new bookmark, and drug it onto the
Personal Toolbar Folder item in the same menu. 

The new bookmark moved, (and appeared above in the toolbar) as it should.

However, after releasing the menu, the sub-menu remained on screen. That is, I
had a box where the submenu was with "Download, Customize, and CoreMail as items.

Submenu remained on screen until I reclicked the Bookmarks menu to help me fill
out this form.

Reproducible: Didn't try
(1) Drag an icon in the URL bar over the Bookmarks folder on the personal
toolbar. The bookmarks menu opens.
(2) Drop the icon in the personal toolbar folder in the bookmarks menu.

Actual result: The bookmarks menu is closed, but the personal toolbar folder
remains open.

Build: 2002081611-trunk/Linux
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows ME → All
*** Bug 177547 has been marked as a duplicate of this bug. ***
(I'm the reporter from bug 177547)

I was unable to reproduce either of the two reports here.  In "my" report, there
are different reports as well as a testcase attachment.

Finally, I don't think there should be a URL attached to this problem as it's
site-independent.
Product: Browser → Seamonkey
Assignee: bugs → nobody
QA Contact: claudius → bookmarks
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
Status: NEW → UNCONFIRMED
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
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.