Closed
Bug 233237
Opened 22 years ago
Closed 21 years ago
hover briefly stops as mouse moves from border to content and back
Categories
(Core :: DOM: Events, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: paul, Unassigned)
References
()
Details
Attachments
(1 file)
|
998 bytes,
text/html
|
Details |
User-Agent:
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040205
On the page (and in the soon to be attached cut down version) is an absolutely
positioned div that changes size and clipping when the mouse is over it using a
CSS :hover pseudoclass.
This works (much better than it did a few days ago, something must have gone in)
but there is a brief flicker as the box is clipped again when the mouse pointer
moves from the border of the div to the insides of the div and vice versa.
Apologies if this is a dupe. There are quite a lot of hover related bugs but I
couldn't find one that really matched this.
Reproducible: Always
Steps to Reproduce:
1.Load page
2.Move mouse to "Other Styles" box
3.Move mouse backwards and forwards from the boxes insides to it's border.
Actual Results:
Box is briefly clipped.
Expected Results:
Box should stay unclipped until mouse leaves div completely
| Reporter | ||
Comment 1•22 years ago
|
||
Comment 2•21 years ago
|
||
I can see the bug, using:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040514
But I can't see the bug anymore in:
Mozilla/5.0 (Windows; U; Windows NT 5.1; @AB_CD@; rv:1.8a4) Gecko/20040924
Firefox/0.9.1+
It seems like this has been fixed somehow by another bug, I think.
| Reporter | ||
Comment 3•21 years ago
|
||
This does indeed seem to be fixed on the 1.8 branch (trunk?)
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122
I'm not sure what the procedure is for this. Should I mark the bug "Fixed" or
change it to the 1.7 branch? Instinctively I'd expect such a bug would probably
be beyond fixing for the stable branch.
Comment 4•21 years ago
|
||
Marking it WORKSFORME. It can only be marked fixed when it is reasonably known
which patch fixed this.
And indeed, this is most likely well beyond fixing for the stable branch.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•