W3C home > Mailing lists > Public > www-style@w3.org > July 2001

Re: @version rule

From: Stuart Ballard <sballard@netreach.com>
Date: Mon, 30 Jul 2001 14:53:51 -0400
Message-ID: <3B65AD3F.E25EC8F1@netreach.com>
To: George Lund <G.A.Lund@bigfoot.com>
CC: www-style@w3.org
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?

Received on Monday, 30 July 2001 14:54:01 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:26:58 UTC