nilref / ie7-js

Automatically exported from code.google.com/p/ie7-js
2 stars 0 forks source link

Specificity is not always preserved for unknown selectors #161

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
These are examples using any combination of class, attribute, and pseudo class 
selectors that 
have a specificity higher than 0030 that do not work. You should be able to 
apply as many of 
these selectors in a single style rule as you want. 

Examples:
SPECIFICITY = 40
.class1.class2.class3.class4{}

SPECIFICITY = 40
.class1 + .class2.class3.class4{}

SPECIFICITY = 40
:not(.class1) + .class2.class3.class4{}

SPECIFICITY = 40
:not(.class1):not(.class2) + [id][class="class3"]

SPECIFICITY = 60
.class1.class2.class3.class4.class5.class6{}

What is the expected output? What do you see instead?
No properties in these styles rules will be applied.

What version of the product are you using? On what operating system?
I experience the same result using IE7.js version 2.0 (beta 3) including 
IE8.js. 

Please provide any additional information below.
I hope this issue can be resolved as quickly as possible

Original issue reported on code.google.com by teamak...@gmail.com on 11 Mar 2009 at 3:05

GoogleCodeExporter commented 9 years ago
This is a know problem cause by the fact that unknown selectors are transformed 
into 
class selectors. I have some heuristics to preserve the specificity but it is 
not 
always possible. I'll try to improve the situation and will keep this issue 
open so 
that others are aware of the problem.

Original comment by dean.edw...@gmail.com on 11 Feb 2010 at 6:27

GoogleCodeExporter commented 9 years ago
Issue 149 has been merged into this issue.

Original comment by dean.edw...@gmail.com on 11 Feb 2010 at 6:53

GoogleCodeExporter commented 9 years ago

Original comment by dean.edw...@gmail.com on 7 Mar 2010 at 6:50