FWIW seems to work in IE7 - dont have IE6 setup at the moment.
On 8/4/07, Cole Kuryakin <[EMAIL PROTECTED]> wrote:
>
> Hello All -
>
> After tearing my hair out for over 4 hours I come to you guys/gals for a
> fresh eye and perhaps a solution.
>
> I've got a simple class name (.active) attached to
you could try adding !IMPORTANT after the colour declaration just to see if
it is an inheritance issue
On 8/4/07, James Gollan <[EMAIL PROTECTED]> wrote:
>
> FWIW seems to work in IE7 - dont have IE6 setup at the moment.
>
> On 8/4/07, Cole Kuryakin <[EMAIL PROTECTED]> wrote:
> >
> > Hello All -
>
When the chosen page loads, the chosen link turns deep red.
The declaration for this is as follows:
/*ACTIVE LINKS ONLY*/
ul#navTopSimpleUL li a.active
{
color: #CC0033;
cursor: default;
text-decoration: none;
}
Hi Cole,,
You may want to also set focus on the element an
the given rule is not using a pseudo selector (:) - it is a simple class
definition. This should be consistent across browsers.
On 8/4/07, Kepler Gelotte <[EMAIL PROTECTED]> wrote:
>
> When the chosen page loads, the chosen link turns deep red.
>
> The declaration for this is as follows:
>
> /*ACT
Hi,
a:active is a pseudoclass, not a class, and the declaration should read:
ul#navTopSimpleUL li a:active
not a.active class name.
Browsers are tolerant of mistakes and try to correct wrong coding in a
meaningful way. However, different browsers may apply different
corrections to the error pr
@Sutart:
I believe that Stuart is using "active" as a class name, not a
pseudoclass.This class is being added to the anchor tag when the
page loads. Not the same as the pseudoclass which is invoked on click,
but does not persist through the subsequent page load.
@Cole:
In my install of I
In the light of the pseudoclass and class having the same name and
smart-alec browsers trying to correct perceived errors, could this
then be a case of misinterpretation by IE6? Might it not be better to
avoid using 'reserved' words for class/id names in case this sort of
thing happened (I
At 19:23 (London time), on 4/8/07, [EMAIL PROTECTED] said:
>In the light of the pseudoclass and class having the same name and
>smart-alec browsers trying to correct perceived errors, could this
>then be a case of misinterpretation by IE6? Might it not be better to
>avoid using 'reserved' wo
