Closed Bug 183502 Opened 23 years ago Closed 22 years ago

Hover causes previously hidden links to display as blocks, but can not actually click on links

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 102578

People

(Reporter: bdmarti, Assigned: saari)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 using styles like this "li ul {display: none;} li:hover > ul {display: block;}" the li will appear when hovered over, however, attempting to click on a link within the li will fail. I found several bugs related to :hover and :active bug 5693 seemed like it referenced a lot of similar cases Reproducible: Always Steps to Reproduce: 1. go to http://www.meyerweb.com/eric/css/edge/menus/demo.html 2. mouseover css/edge 3. attempt to click a link on the menu that appears Actual Results: the display: block <li> tag disappears, apparently returning to it's previous display: none state The browser does NOT follow the link that was clicked on Expected Results: the browser should have changed locations to that of the link I was trying to click on
worksforme, linux trunk build 2002-12-04-05.
this is behaving like bug 132592, although this would be the first case of that bug occuring with purely CSS (not JS).
WFM, day old trunk CVS, Linux. All links in the submenus on the "css/edge" work fine.
Depends on: 102578
*** Bug 192065 has been marked as a duplicate of this bug. ***
Boris - Can you confirm this bug now?
the problem I mentioned in comment 2 not JS/CSS-specific. actually, quite a few of the bug 102578 dupes have been reported with the URL mentioned here. marking dupe *** This bug has been marked as a duplicate of 102578 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
No longer depends on: 102578
Resolution: --- → DUPLICATE
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.