Closed Bug 256684 Opened 20 years ago Closed 20 years ago

Mixing class and id selector prevent proper rendering

Categories

(Core :: CSS Parsing and Computation, defect)

defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: wolruf, Assigned: dbaron)

References

()

Details

(Keywords: testcase)

build ID: 20040823 Win2k, Linux, Firefox trunk

Steps to reproduce:
1. Load first testcase:
http://wolruf.free.fr/mozbug/css/test.html
The text doesn't render as green in Gecko, it renders green in Safari 1.2, IE6,
Opera 7.54

2. Load second testcase, only difference is that the CSS lines are splitted:
http://wolruf.free.fr/mozbug/css/test2.html
It renders green in Gecko and other browsers.
The ID starts with a number. Since an ID MUST NOT start with a number it is an
invalid ID. If one selector isn't correct the whole selector rule should be
ignored. I suggest you send a mail to Opera to report the bug.

<http://www.w3.org/TR/html401/types.html#type-name>
<http://www.w3.org/TR/2004/CR-CSS21-20040225/syndata.html#q10>
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Anne, thanks a lot for your analysis, if I may, can I ask you one more thing ?

Mozilla 1.7b render both in green whereas 1.7RC1 renders it black, so this
behavior changed between 1.7b and 1.7RC1.
I couldn't find the appropriate bug report.

I'm simply wondering if it's an unwanted regression or a feature that could be
maybe only required in strict compliance mode and left away in quirks mode ?
Thanks to Callek on #css, this was implemented with bug 239079.
In that case...
Status: RESOLVED → REOPENED
Resolution: INVALID → ---

*** This bug has been marked as a duplicate of 239079 ***
Status: REOPENED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → DUPLICATE
No, this bug is the opposite.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Status: REOPENED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → INVALID
Should have known...
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.