Could Overqualified Elements check rest of usage?

[LeeKowalkowski]

For a class, if every occurrence of element.my-class is div.my-class, then of course that looks overqualified and unnecessary. But if I have li.my-class dt.my-class and dd.my-class, then they do not appear to be overqualified.

I think this warning should only be displayed if every occurrence of element.class is a reference to the same HTML tag name.

[dpie]

Agreed. Here's an example of how CSS Lint is flagging elements as overqualified when it shouldn't.

li.last {
  margin-bottom: 2px;
}

p.last {
  margin-bottom: 10px;
}

This results in two warnings:

Overqualified Elements
Element (li.last) is overqualified, just use .last without element name.

Overqualified Elements
Element (p.last) is overqualified, just use .last without element name.

If the author was to reduce both selectors down to .last as suggested, all elements with that class would receive the compiled sum of both styles (in this case, margin-bottom:10px), which isn't the intention of the CSS code.

[nzakas]

Interesting point. Definitely something we can look into.

[nzakas]

Nicole, what do you think on this one?

[stubbornella]

good point.

I can think of another example:

.message{} //most code here
p.message{} //exceptions for block level elems here
strong.message{} // exceptions for inline elements here

Seems like a good change to me.