Closed Bug 225478 Opened 21 years ago Closed 21 years ago

Can't click on <a> element with :hover and :after

Categories

(Core :: CSS Parsing and Computation, defect)

Product:
Core
Component:
CSS Parsing and Computation
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: xanthor+bz, Assigned: dbaron)

References

(
URL
)

Details

(Keywords: css3) 

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031008
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031008

When we define in CSS a style with the pseudo selectors :hover:after with a
content (for exemple adding a flag after a link when the mouse is over it), we
can't click on this link.
Ctrl+clik, middle click, and right click works, but not left click.

Reproducible: Always

Steps to Reproduce:
1. Write a CSS line lite : a:hover:after {content : 'what you want';}
2. Try to click on a link with this style
Actual Results:  
When we click on the link, nothing occures

Expected Results:  
Mozilla should load the linked page, with the same behaviour if it was no style

Tested with : Mozilla 1.4.1, Firebird 0.7, Epiphany 1.0.3, in differents debians
and on a Mandrake

Seems to work with windows...
If I am not mistaken,  this is a duplicate of bug 46891
I don't think so : bug 46891 don't talk about :hover selector
Without it, the test works for me...

(I add that this bug has been confirmed with a firebird 0.7 on RH)
Worksforme  with a current linux build, actually.  This got fixed in bug 188525
and I don't see any reason it would have regressed...

Reporter, what windowmanager are you using?
I'm using sawfish 1.3, but the bug has been confirm with kwm and xfwm (I don't
know which version)
Keywords: css3
Try twm of fvwm or some other sane WM... if it goes away, it's probably bug 102578
Depends on: 102578
I have not yet attempted to recreate the test case.

I strongly suspect this bug is addressed by the checkin for 102578.
Yes, it's fixed.
Sorry for the delay...

(I change the bug to resolved. Correct me if I shouldn't...)
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.