- From: Ian Hickson <ian@hixie.ch>
- Date: Mon, 30 Jul 2001 13:15:29 -0700 (Pacific Daylight Time)
- To: Stuart Ballard <sballard@netreach.com>
- cc: George Lund <G.A.Lund@bigfoot.com>, <www-style@w3.org>
On Mon, 30 Jul 2001, Stuart Ballard wrote:
> George Lund wrote:
> >
> > What is needed is a mechanism for grouping CSS rules, such that either
> > they are all rules in the group are applied or none are. This would
> > allow user and author stylesheets to interact without the risk that a
> > setting in one, while not overriding the setting in another, render the
> > page unreadable. The present situation leaves a serious risk of this
> > happening especially when fixed positioning is used.
>
> Seems to me that this would also be entirely consistent with backward
> compatibility; eg:
>
> @combine {
> selector1 { attr1: val1 };
> selector2 { attr2: val2 };
> }
>
> If the defined behavior for "@combine" was "either all should succeed or
> all should fail", then it would be interpreted correctly by UAs that
> don't understand @combine: all would fail!
>
> Thoughts? Anyone in the WG think this is an idea worth pursuing, or
> should we all just give up and go home?
I think if it means "only apply the contents of this rule if you
understand every single selector, @rule and property" then it would be a
worthy addition. However, 'understand' is not the same as 'support'.
Mozilla understands (parses) a few CSS2 properties and keywords that it
then promptly ignores when rendering (e.g. all the aural properties).
--
Ian Hickson )\ _. - ._.) fL
Invited Expert, CSS Working Group /. `- ' ( `--'
The views expressed in this message are strictly `- , ) - > ) \
personal and not those of Netscape or Mozilla. ________ (.' \) (.' -' ______
Received on Monday, 30 July 2001 16:15:29 UTC