Re: [css3-cascade] browser specific CSS

Tab Atkins Jr.:
> 
> The one area where we *do* want to do something, imo, is in making CSS capable of doing feature-testing.  This has been proposed in the group before, via an @supports rule.

I liked the ‘!required’ solution:

  foo {
    bar: plain and simple; /* fallback */
    bar: bells and whistles !required;
    baz: only works well with second bar !required;
  }

This hardly works across rulesets and only provides one level of fallback, but it is good enough for many use cases.

Received on Friday, 1 April 2011 08:28:45 UTC