I shoud imagine its these two rules that is causing a bit of ambiguity :
.album *
{
position: absolute;
z-index: 0;
}
.albumSub
{
z-index: 100;
position: absolute;
/* other stuff */
}
I am guessing that the first rule is given a higher specificity,
however according to [1] the * should not give it any higher
specificity, but it isn't absolutely clear about the subject. I guess
its a different interpretation of the standard.
If I were you I'd not use the wildcard selector because its not
immediately obvious. You can target the a element for that. Then I'd
override that with the second rule, using .album as an extra class
name to increase its specificity :
.album a
{
position: absolute;
z-index: 0;
}
.album .albumSub a
{
z-index: 100;
position: absolute;
/* other stuff */
}
HTH
Sam
[1] http://www.w3.org/TR/CSS21/cascade.html#specificity
On 02/05/06, Bostjan Kern <[EMAIL PROTECTED]> wrote:
> Hi!
>
> URL: http://neovizija.com/emanuel/
>
> Problem: The element with z-index: 0; is overlapping the element with
> z-index: 100.
>
> It works fine in Safari, Firefox and Opera though.
>
> Any ideas how to *fix* this?
>
> Cheers,
> Bostjan :)
> ______________________________________________________________________
> css-discuss [EMAIL PROTECTED]
> http://www.css-discuss.org/mailman/listinfo/css-d
> IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
> List wiki/FAQ -- http://css-discuss.incutio.com/
> Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
>
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
