Closed Bug 181617 Opened 22 years ago Closed 21 years ago

Items in Get Msgs dropdown show unrelated tooltip (whichever was previously shown)

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows XP
defect
Not set
trivial

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 147670

People

(Reporter: maxbowsher, Assigned: sspitzer)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016

.

Reproducible: Always

Steps to Reproduce:
1. Hover over a toolbar button (Compose, for example) until a tooltip appears.
2. Click the down arrow of the Get Msgs button.
3. Hover over a menu item in the Get Msgs dropdown until a tooltip is displayed.

Actual Results:  
The tooltip from the Compose (or other) button is displayed.

Expected Results:  
No tooltip should be displayed. (Or at least I can't think of anything useful to
show for the items in this menu.)
I also see this with 2002112204 on Win2k.

(When you do *not* get another tooltip before, "Get new messages" is displayed
as tooltip, which is correct and does make sense)
I suspect that that is just a side effect of the bug, though. Its hardly
necessary to have a tooltip saying 'Get new messages' in a 'Get Msgs' menu.
This bug also occurs for the dropdown menu from the 'File' toolbar button.
Whiteboard: DUPEME
DUPEME? Really? With which bug#? I searched pretty carefully before filing this.
fix for bug 71329 might to fix this.
Other variants are bug 79240 and bug 147670
QA Contact: olgam → laurel
Not a dupe of bug 71329 or bug 79240, as far as I can tell; this is about 
tooltips over the menus, not the dropdown widget on the toolbar. 

Note that Kyle said in the duplicatee, tooltips over the menus shouldn't even be 
there.

*** This bug has been marked as a duplicate of 147670 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.