>
>
>> Here is the HTML:
>>
>> <div id="yoo-toppanel-1"
>> class="yoo-toppanel">content</div>
>>
>> And it reads this CSS first:
>>
>> #yoo-toppanel-1 div.yoo-toppanel div.panel-container {
>>
>> But because of this it is disregarding 'mine' and choosing
>> default.
>
> Hi Chris,
>
> It's actually 'disregarding' your CSS because '#yoo-toppanel-1
> div.yoo-toppanel' doesn't match; that's looking for a DIV element
> with a class of 'yoo-toppanel' INSIDE an element with an ID of 'yoo-
> toppanel-1'.
>
> To match that element, you actually want:
>
> #yoo-toppanel-1.yoo-toppanel
>
> OR
>
> div#yoo-toppanel-1.yoo-toppanel
>
> OR just
>
> #yoo-toppanel-1
>
> which will probably 'win' on specificity, depending on the other CSS
> present.
>
> - Bobby
>
You inspired me to give it another crack and what i did was change:
#yoo-toppanel-1 div.panel-container{ -to- div#yoo-toppanel-1
div.panel-container {
and it's worked!
I don't understand why every class or ID in this module's default CSS
has to start with 'div' but that's what'd been crushing my change in
parenting idea. I guess that IDs are stronger than classes then.
______________________________________________________________________
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
