The Solution

It was related to a pseudo selector in CSS, :hover to be exact. I’ll simplify it so it won’t look exactly like what it did on GameSpot. The line was incorrectly coded.

Problem

1

#some_container .anchor:hover{text-decoration:underline;}

Solution

1

#some_container a.anchor:hover{text-decoration:underline;}

Do you see the difference there? The incorrect way was missing the “a”. I’m not totally positive why this would cause IE7 to hiccup but my theory is that IE7 was trying to apply :hover onto the element with the “anchor” class, but had trouble finding it. And because the thread was so long, IE7 MAY have been trying to render and apply the rule to the element with the “anchor” class. Another thing is that the rule wasn’t even being applied in the forum pages, which makes things odd.

The Code

1
2
3
4
5
6
7

//Add the pseudo selector
Selectors.Pseudo.has = function(arg){
    return (this.getElement(arg)) ? this : false;
}
 
//Returns anchors that has img elements
$$('a:has(img)');

But, correct me if I’m wrong, we can’t do the following and expect the same thing:

1
2

// returns an array of img elements, instead of anchors
$$('a < img');

What do you guys think? Is this the way to go for the pseudo “has” selector?