W3C home > Mailing lists > Public > www-style@w3.org > September 2012

Re: [css-variables] Non-inherited custom properties (Issue 5)

From: Roland Steiner <rolandsteiner@google.com>
Date: Fri, 7 Sep 2012 11:59:31 +0900
Message-ID: <CACFPSpg1o-hu1ej-__8-beVJpJd0=gW+J1LarLK1y42ssujP3A@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: François REMY <fremycompany_pub@yahoo.fr>, CSS WG <www-style@w3.org>
One case could be if you would like to flag an element, but not have the
same applied to nested elements. For example, highlighting a moderator in a
nested list of messages:

<div class="message">
    <div class="moderator message">
        <div class="message >

.moderator {
    var-highlight-color: #fe6;
}

.message {
    background-color: var(highlight-color, #eee);
}

This would also apply the highlight to the nested message, which is not
intended. With components, this becomes even more interesting, as you would
want to inherit across the shadow boundary, but not within the main DOM
(e.g., just replace <div> with <x-message> above).

That said, there should be a workaround in that one can just reset the
variable at every applicable element and have that overridden by more
specific rules:

.message {
    var-highlight-color: initial;
    background-color: var(highlight-color, #eee);
    // using a fallback in case more specific rule may reset to 'initial'
as well
}

.message.moderator {
    var-highlight-color: #fe6;
}


- Roland



On Fri, Sep 7, 2012 at 4:11 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:

> On Thu, Sep 6, 2012 at 2:48 AM, François REMY <fremycompany_pub@yahoo.fr>
> wrote:
> > There have been many request for non-inherited custom properties.
> However,
> > it’s impossible to specify them in the file in a good way, which makes
> them
> > basicly impossible.
> >
> > My proposed solution (don’t necessarily assume Brian and Chris support on
> > this) would be a ‘use-declared()’ function that only takes in
> consideration
> > the specified value of the referenced property if it was explicitely
> defined
> > on the element (so, not if its initial state or inherited value are in
> use).
>
> I'm interested in solving this, either at the point of reference (as
> you suggest) or at the point of definition (in the custom property).
>
> However, I'm not sure it *needs* to be solved.  Do you have some
> examples of things that are problematic if variables always inherit?
>
> ~TJ
>
>
Received on Friday, 7 September 2012 03:00:20 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:59 GMT