A test page is here:
<!-- m --><a class="postlink" href="http://newsdf.tripod.com/webforum/hoverpower.html">http://newsdf.tripod.com/webforum/hoverpower.html</a><!-- m -->
(Omitted implied <body> tags again; they don't affect the matter)
That page validates
In the page there is a little link. That little link contains an even more little span. Hence, the little little span is a child of the little link.
When we put our CSS glasses on, we see not one, not two, but four of the little links, sometimes simultaneously. May be the little link has gone crazy, but it is more likely that I am talking about pseudo classes.
Now, before you know it, two vicious big browsers are here with the most evil intents. One, called Mozilla, grabs the whole chunk of code with the little link and the little link's only child and rushes it off to a visitor. Mozilla may be big and vicious, but it brings the visitor everything as the author intended. The other browser, called Ie, is much more cunning... It grabs the chunk of code, but before Ie's user sees it, Ie does horrible things to the little link: it eats one of its pseudo classes. And as luck has it, the pseudo class was called 'hover', the one, which would bring the most happiness to Ie's user. And the deprived user ends up not knowing that the little link had 'hover' at all, or more precisely, there will be 'hover' for the little link, but there will be no 'hover' for the children.
Alas for the poor little little span! This story has no happy ending.
Why cannot the big cunning Ie display a little link PROPERLY, even when a colour has been specified for all of the link's pseudo classes?Originally posted by King Pellinore
Why cannot the big cunning Ie display a little link PROPERLY, even when a colour has been specified for all of the link's pseudo classes? [/B]
Becuse it like to be special?
<!-- m --><a class="postlink" href="http://newsdf.tripod.com/webforum/hoverpower.html">http://newsdf.tripod.com/webforum/hoverpower.html</a><!-- m -->
(Omitted implied <body> tags again; they don't affect the matter)
That page validates
In the page there is a little link. That little link contains an even more little span. Hence, the little little span is a child of the little link.
When we put our CSS glasses on, we see not one, not two, but four of the little links, sometimes simultaneously. May be the little link has gone crazy, but it is more likely that I am talking about pseudo classes.
Now, before you know it, two vicious big browsers are here with the most evil intents. One, called Mozilla, grabs the whole chunk of code with the little link and the little link's only child and rushes it off to a visitor. Mozilla may be big and vicious, but it brings the visitor everything as the author intended. The other browser, called Ie, is much more cunning... It grabs the chunk of code, but before Ie's user sees it, Ie does horrible things to the little link: it eats one of its pseudo classes. And as luck has it, the pseudo class was called 'hover', the one, which would bring the most happiness to Ie's user. And the deprived user ends up not knowing that the little link had 'hover' at all, or more precisely, there will be 'hover' for the little link, but there will be no 'hover' for the children.
Alas for the poor little little span! This story has no happy ending.
Why cannot the big cunning Ie display a little link PROPERLY, even when a colour has been specified for all of the link's pseudo classes?Originally posted by King Pellinore
Why cannot the big cunning Ie display a little link PROPERLY, even when a colour has been specified for all of the link's pseudo classes? [/B]
Becuse it like to be special?