Open Bug 642270 Opened 15 years ago Updated 3 years ago

Toplevel drop down menus unresponsive

Categories

(Firefox :: Menus, defect)

Product:
Firefox
Component:
Menus
Platform:
x86
macOS
Type:
defect

Tracking

()

People

(Reporter: xtianbloom, Unassigned)

Details

FF 4 RC1 This happened on an earlier Beta version of FFx4 as well. Navigated to http://stackoverflow.com/tags/mysql/topusers and noticed that toplevel drop down menus no longer appear, no matter what I do with my mouse. Contextual menus work just fine.
Which top level drop down menus do you mean? The main menu or some drop downs in the web page? Do you see any error in the error console? Does it also happen in Safe Mode or a fresh profile?
Version: unspecified → Trunk
I see no errors in the console or even warnings when I hover over things like Questions, Tags, Users. When I hover over the MySQL bluish button I get an info box. Other links that look like top-level menus don't appear to drop down any options.
I mean the very top menus (Firefox File Edit...etc..) The problem oddly went away after 30-40 minutes. Afraid I didn't check the error console. Since the problem is gone, too late to try to reproduce it in Safe Mode or with a Fresh profile. Sorry. If it happens again, I see what I can do.
Happened while browsing profiles in LinkedIn Recruiter - the url wouldn't help you reproduce the experience, since it's specific to my account and session. I browse LinkedIn profiles a lot, so it's weird. 1) created a new profile, started FFx with that profile, while leaving default profile session open: new profile session, everything worked fine 2) error console: no errors listed, just a bunch of warnings, and a single message (www.linkedin.com : server does not support RFC 5746, see CVE-2009-3555). Have screen shots of the first two pages or console Warnings, if that would help. 3) a regular restart in my default profile cleared it up
Could you please create a screencast which visualizes your issue? That would be kinda helpful. Thanks.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.