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

VERIFIED FIXED in mozilla6

Status

()

Core
CSS Parsing and Computation
P4
major
VERIFIED FIXED
15 years ago
4 years ago

People

(Reporter: Sergey «Mithgol the Webmaster» Sokoloff, Assigned: dbaron)

Tracking

(Depends on: 1 bug, {dev-doc-complete})

Trunk
mozilla6
dev-doc-complete
Points:
---
Bug Flags:
in-testsuite ?

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

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 http://mithgol.pp.ru/Mozilla/hoverbug.htm 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 http://mithgol.pp.ru/Mozilla/hoverbug.htm 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
also.
(Assignee)

Comment 1

15 years ago
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
http://mozilla.org/docs/web-developer/quirks/ ), then you won't have to deal
with these quirks.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → WONTFIX
Hmm...

You could at least mention it in your quirklist at
http://mozilla.org/docs/web-developer/quirks/quirklist.html - 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?
(Assignee)

Comment 3

15 years ago
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...)
Status: RESOLVED → VERIFIED

Comment 5

13 years ago
*** Bug 244065 has been marked as a duplicate of this bug. ***
(Assignee)

Comment 6

12 years ago
*** Bug 297950 has been marked as a duplicate of this bug. ***
(Assignee)

Updated

8 years ago
Duplicate of this bug: 219853
(Assignee)

Updated

8 years ago
Duplicate of this bug: 232757
(Assignee)

Updated

8 years ago
Duplicate of this bug: 501281
(Assignee)

Updated

8 years ago
Duplicate of this bug: 533653
(Assignee)

Updated

8 years ago
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
(Assignee)

Comment 11

8 years ago
Bug 501281 comment 6 says:
> > This is a known quirks mode behavior:
> > https://developer.mozilla.org/en/Mozilla%27s_Quirks_Mode
> > 
> > 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
(Assignee)

Comment 13

7 years ago
I think we can probably remove this quirk; WebKit doesn't have it.  (Or do they have a different variation of it?)
Status: VERIFIED → REOPENED
Ever confirmed: true
Resolution: WONTFIX → ---
(Assignee)

Updated

7 years ago
Duplicate of this bug: 595476
QA Contact: ian → style-system
(Assignee)

Updated

6 years ago
Duplicate of this bug: 635654

Updated

6 years ago
OS: Windows 2000 → All
Hardware: x86 → All
(Assignee)

Comment 16

6 years ago
Created attachment 527890 [details] [diff] [review]
patch
Attachment #527890 - Flags: review?(bzbarsky)
Comment on attachment 527890 [details] [diff] [review]
patch

r=me
Attachment #527890 - Flags: review?(bzbarsky) → review+
(Assignee)

Comment 18

6 years ago
https://hg.mozilla.org/mozilla-central/rev/b7b5af018848
Status: REOPENED → RESOLVED
Last Resolved: 15 years ago6 years ago
Priority: -- → P4
Resolution: --- → FIXED
Target Milestone: --- → mozilla6

Updated

6 years ago
Flags: in-testsuite?

Comment 19

6 years ago
Changed
https://developer.mozilla.org/en/Mozilla_Quirks_Mode_Behavior

Needed here also?
https://developer.mozilla.org/en/Firefox_6_for_developers
Keywords: dev-doc-needed
I cleaned up the edit here:

https://developer.mozilla.org/en/Mozilla_Quirks_Mode_Behavior

And added a note on Firefox 6 for developers. Thanks!
Keywords: dev-doc-needed → dev-doc-complete

Updated

6 years ago
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.
Status: RESOLVED → VERIFIED

Updated

4 years ago
Depends on: 945607
You need to log in before you can comment on or make changes to this bug.