Hi Simon,
I just read this thread, and I was going to suggest using an alias.
I think your idea is fine.
- Jeanne
Simon Lessard wrote:
Hello again,
I thought about a 4) last night for this, I could also import
af|panelBox::body in the 4 selectors, basically using it as an alias.
Is it
reasonable?
On 10/30/06, Simon Lessard <[EMAIL PROTECTED]> wrote:
Yes we got one. I'll add the issue a bit later tonight.
On 10/30/06, Adam Winer <[EMAIL PROTECTED]> wrote:
>
> I agree... though this is confusing... I can't
> think of anything better, though.
>
> Do we have a Wiki page yet for skinning? This'd
> be a good thing to throw up there.
>
> -- Adam
>
>
> On 10/30/06, Simon Lessard <[EMAIL PROTECTED]> wrote:
> >
> > Hello all,
> >
> > There was a post this morning about a skin selector not working in
> > panelBox
> > (my implementation). Anyway, the user was trying to use the
following:
> >
> > af|panelBox::body {
> > background-color: black;
> > }
> >
> > However, the background was not changing. This is because simple
skin
> > defines af|panelBox::light af|panelBox::body {background-color:
> aColor;}
> > and
> > it get generated after the root selector in the final CSS, thus
giving
> it
> > priority.
> >
> > There's three way to fix that:
> >
> > 1) Users can overload the 4 selectors (for each background) to
set the
>
> > desired color;
> > 2) Users can use af|panelBox::body, but overload all 4 other body
> > selectors
> > in order to inhibit the inherited property;
> > 3) Remove colors from simple skin and move them to minimal instead.
> >
> >
> > Personally I think users should opt for 2) and we should not change
> simple
> > skin. Anyone has comments about that?
> >
> >
> > Regards,
> >
> > ~ Simon
> >
> >
>
>
