TYPO3 Core

I would like to "bump" this bug since it seems to be very old, but it didn't get fix yet.
Actually I can't really ask for a "fix" since it's not a bug, but I would love to get 100% result on my page speed tests.

Anyways, 4 years later (2013), the issue still exists. Below the rules it nags about:

Very inefficient rules (good to fix on any page):

DIV.csc-textpic .csc-textpic-imagewrap table    Tag key with 2 descendant selectors and Class overly qualified with tag
    DIV.csc-textpic .csc-textpic-imagewrap table tr td    Tag key with 4 descendant selectors and Class overly qualified with tag
    DIV.csc-textpic .csc-textpic-imagewrap FIGURE    Tag key with 2 descendant selectors and Class overly qualified with tag
    DIV.csc-textpic-border DIV.csc-textpic-imagewrap IMG    Tag key with 2 descendant selectors and Class overly qualified with tag and Class overly qualified with tag
    DIV.csc-textpic .csc-textpic-imagewrap IMG    Tag key with 2 descendant selectors and Class overly qualified with tag

Inefficient rules (good to fix on interactive pages):

UL.csc-uploads LI    Tag key with descendant selector and Class overly qualified with tag
    UL.csc-uploads LI    Tag key with descendant selector and Class overly qualified with tag
    UL.csc-uploads IMG    Tag key with descendant selector and Class overly qualified with tag
    UL.csc-uploads SPAN    Tag key with descendant selector and Class overly qualified with tag

I've come up with a solution though. I don't know if this is possible to make with the current setup, but here it goes:

Instead of using those selectors, just use the class tag like this:

<ul class="csc-uploads">
    <li class="csc-uploads-li"></li>
    <img class="csc-uploads-img" />
    <span class="csc-uploads-span"></span>
    </ul>

And use the following CSS code:

ul.csc-uploads
    li.csc-uploads-li
    img.csc-uploads-img
    span.csc-uploads-span

The above example should fix all errors in the "inefficient rules" section.
The same can be applied, of course, to the "very inefficient rules" section.

I hope you will pay some attention to this, as I am told that inefficient rules can slow the website down with (sometimes) as much as 20ms a tag!!
Also, I think uppercase HTML is a bit oldskool.. Perhaps it's better to use small case HTML/CSS (DIV.csc-textpic => div.csc-textpic) but that's just a suggestion.

Hey Patrick, can you have a look at this issue please while refactoring the Content Elements?

We now have fluid_styled_conten which comes with a lot of cleaner and less CSS code. Thus, we can close this one. If not, please let me know.