Closed Bug 197686 Opened 17 years ago Closed 9 years ago

:hover (dynamic pseudo-class) doesn't work after class selectors with no tag name in quirks mode


(Core :: CSS Parsing and Computation, defect, P4, major)






(Reporter: mithgol, Assigned: dbaron)


(Depends on 1 open bug, )


(Keywords: dev-doc-complete)


(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312

After upgrading to Mozilla 1.3, I've seen major CSS2 functionality loss. :hover
(dynamic pseudo-class) doesn't work after universal class selectors
(.classname:hover), where it worked in Mozilla 1.2.1. Still it works in
TAGNAME:hover (see for test case).

All that makes me greatly upset. Probably we'll need Mozilla 1.3.1 really soon,
since several CSS2 menus are lost. Imagine .classname:hover { visiblity: ... };

Reproducible: Always

Steps to Reproduce:
1. Enter in location field.
2. Load the page, follow the instructions.
3. Note that Mozilla 1.3 and 1.2.1 behave differetly.

Actual Results:  
Class .test:hover (see page source) doesn't work in Mozilla 1.3. A major feature
is broken; I'll set bug priority to Major.

Expected Results:  
Class .test:hover should work as in Mozilla 1.2.1, according to W3C
specification docs.

Tested under Win2000 and Win98, the same results.

I'm not completely sure that component is "Style System"; check it for yourself
This was done intentionally, but in quirks mode only.  See bug 169078.  (It was
done because allowing this breaks a bunch of web pages that expect :hover to
apply only to links.)

If your page has a doctype that puts the browser into standards mode (see ), then you won't have to deal
with these quirks.
Closed: 17 years ago
Resolution: --- → WONTFIX

You could at least mention it in your quirklist at - it's "Last
modified August 20, 2002", that's really old.

Your advice sounds really funny, my documents never validate under strict
validators, that's why I never used any !DOCTYPE, so what am I forced to do with
this quirk? To invent my own doctype?
You could just add "<!DOCTYPE html>"
Verified.  If your page is tag soup, it gets treated as tag soup (and you can
validate to Transitional and still have a doctype, you know...)
*** Bug 244065 has been marked as a duplicate of this bug. ***
*** Bug 297950 has been marked as a duplicate of this bug. ***
Duplicate of this bug: 219853
Duplicate of this bug: 232757
Duplicate of this bug: 501281
Duplicate of this bug: 533653
Summary: :hover (dynamic pseudo-class) doesn't work after universal class selectors in Mozilla 1.3 → :hover (dynamic pseudo-class) doesn't work after class selectors with no tag name in quirks mode
Bug 501281 comment 6 says:
> > This is a known quirks mode behavior:
> >
> > 
> > Is it not present in other browsers anymore?
> Opera 10b and WebKit/Safari4 do not have this Quirk (anymore). IE 8 mimics IE6
> & 7 (and Gecko) in quirks mode.
Duplicate of this bug: 586031
I think we can probably remove this quirk; WebKit doesn't have it.  (Or do they have a different variation of it?)
Ever confirmed: true
Resolution: WONTFIX → ---
Duplicate of this bug: 595476
QA Contact: ian → style-system
Duplicate of this bug: 635654
OS: Windows 2000 → All
Hardware: x86 → All
Attached patch patchSplinter Review
Attachment #527890 - Flags: review?(bzbarsky)
Comment on attachment 527890 [details] [diff] [review]

Attachment #527890 - Flags: review?(bzbarsky) → review+
Closed: 17 years ago9 years ago
Priority: -- → P4
Resolution: --- → FIXED
Target Milestone: --- → mozilla6
Flags: in-testsuite?
I cleaned up the edit here:

And added a note on Firefox 6 for developers. Thanks!
Duplicate of this bug: 667964
Mozilla/5.0 (Windows NT 5.1; rv:8.0a1) Gecko/20110719 Firefox/8.0a1

Verified issue on Win XP, Win 7, Ubuntu 11.04 and Mac OS x 10.6 - using the test case from Bug 635654 that was marked as a duplicate of this one (Bug 197686). 

Setting resolution to VERIFIED FIXED.
Depends on: 945607
You need to log in before you can comment on or make changes to this bug.