Closed Bug 166839 Opened 23 years ago Closed 23 years ago

Status bar always displays Document: Done; Tooltips don't work; sub-menus don't work: OnMouseOut firing too early?

Categories

(Core :: XUL, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mail, Assigned: jag+mozilla)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826 Hello, Sorry if this is a duplicate bug, or under the wrong category, but I'm experiencing these problems in Windows XP only. Under Windows 2000 and Linux, everything behaves as I would expect. That's why I'm filing a new bug here. These problems have occured in Mozilla 0.9, 1.0, and 1.1 on this same computer--but when I loaded 1.1 on Windows 2000, and 1.1 on Linux, no problems. Reproducible: Always Steps to Reproduce: 1. Hover over any link. 2. Hover over any link that has text in a "title=" attribute. 3. Right-click in a frame and attempt to view frame source. Actual Results: 1. Status bar flashes the URL, but immediately reverts to "Document: Done". 2. No tooltip text appears (it does in other OS's). 3. Context menu appears, but you cannot expand sub-menus, such as "This Frame ->", either by hovering or clicking on them. Expected Results: 1. URL appears in status bar and stays there until mouse leaves link. 2. Tooltip appears for specified period of time. 3. Sub-menu expands, items highlight when you roll over them. I've looked for relevant preferences and bugs, but haven't found any that seem to address this issue. Perhaps there's some setting I've missed? If so, I highly apologize, and hope someone will direct me to the solution. But this is making it hard to use Mozilla on my main machine--and I otherwise think Mozilla is great... Cheers, John
WFM, Mozilla 1.1, Windows XP, Gecko/20020826 Status bar changes properly, Tooltips appear, Submenus cascade fine. Have you tried uninstalling and reinstalling Mozilla? I've had that fix a few weird issues.
Well, I had reinstalled Mozilla 3 times, upgrading versions... But I deleted my profile, and the new one works fine. Must've been some odd leftover setting in my old Netscape profile or something. No problem, now. Thanks for the tip, sorry to waste bandwidth here... --John
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
It's back... Actually, now what's happening is the first time I open Mozilla after rebooting, the mouseover/mouseout events occur as they should. But after visiting a frameset page (my email web page, which is Squirrelmail on an internal server) and clicking a link in one frame that loads content in another frame, the onmouseout event seems to fire before the mouse leaves the element. Hovering over hyperlinks, the status bar flashes the link URL, and then immediately goes to "Document Done(0.xxx seconds)". Thereafter, the mouseout event fires too early in all Mozilla windows, inside frames, tabs, or nothing. Closing and restarting Mozilla has no effect. Only rebooting resets the behavior. Again, this only happens on Windows XP Pro (the same page viewed from Mozilla on Win2K and Linux does not reproduce the bug). I've tried removing/reinstalling Mozilla (no effect) and deleting the profile (which made the problem go away temporarily). Is there some file I should attach to aid in troubleshooting this?
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
WFM with 2002111211/trunk/win2k. reporter (John): can you reproduce this bug with a recent build of mozilla (for example, 1.2beta)? if so, please comment again with details. if not, please resolve this bug as WORKSFORME. thanks.
no response from reporter for 30 days, resolving WORKSFORME. reporter: if you can reproduce this bug with a recent build of mozilla (for example, 1.2.1), please reopen this bug and give details. thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.