datepicker dropmarker may not be manifesting :hover and :active CSS pseudo-classes

UNCONFIRMED
Unassigned

Status

()

UNCONFIRMED
12 years ago
11 years ago

People

(Reporter: mcdavis941.bugs, Unassigned)

Tracking

Trunk
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a8pre) Gecko/2007080309 Minefield/3.0a8pre

I'm not certain, but it seems like the dropmarker on a popup-type datepicker isn't manifesting the :hover and :active CSS pseudo-classes on mouseover and mouseclick.

I've got some CSS rules that should be triggered for the dropmarker on :hover and :active, but they aren't.  If I manually set the pseudo-classes in DOM Inspector, then the rules trigger as expected.

Reproducible: Always

Comment 1

12 years ago
> I've got some CSS rules that should be triggered for the dropmarker on :hover
> and :active, but they aren't.

It would be interesting to see the rules... And also how/where you've added them.

Version: unspecified → Trunk
Created attachment 275354 [details]
for testing datepicker element -- CSS to follow
@stefanh: I just attached the XUL I'm using as a testcase.  The CSS is part of a custom theme; I'll cut out the relevant CSS and attach separately.  In the mean time, please let me know if you see any problems with the XUL itself.
Created attachment 275360 [details]
CSS for datepicker dropmarker, extracted from datetimepicker.css

Comment 5

12 years ago
Have you tried !important on the relevant style rules? That said, unfortunately, I'm on mac so I'm not really the right person... I can just speculate - maybe your style rules get overruled by the style rules in dropmarker.css? DOMi should show that, though.
(In reply to comment #5)
> Have you tried !important on the relevant style rules? 

Yes, to no effect.

Really though, it seems to me the problem is not the rules, since they fire correctly when I manually add :hover to the element.

You need to log in before you can comment on or make changes to this bug.