W3C home > Mailing lists > Public > www-style@w3.org > January 2004

Re: [CSS] Rules for parsing and compatibility

From: Mikko Rantalainen <mira@cc.jyu.fi>
Date: Tue, 30 Dec 2003 08:39:51 -0500 (EST)
Message-ID: <3FF17EF4.2080204@cc.jyu.fi>
To: Stanimir Stamenkov <stanio@myrealbox.com>
Cc: www-style@w3.org

Stanimir Stamenkov / 2003-12-30 14:58:
> Jukka K. Korpela wrote:
>> On Sun, 28 Dec 2003, Stanimir Stamenkov wrote:
>>> The thing is to address the different level of UAs support of
>>> the CSS spec and the new versions of it.
>> I think the issue is much broader, and very important. [...] It
>> could be defined so that @tie { ... } means that a UA should
>> ignore all the rules contained unless it can and will implement
>> them all.
> First I've though of specifying a special prefix keyword in the 
> selectors like (I will use "tie" as you've mentioned):
> !tie E { -x-whatever-foo: bar; }

I think an AT rule is better because the !tie approach cannot handle 
the case where rules should be applied to group of elements or none 
at all. For example, if I had rules like

	background: black;
div.special *
	color: yellow;

I'd really hate if only one of the rules would be applied. (Assume 
that I've some real reason not to specify color and background for 
every element.) If, on the other hand, I could wrap the whole thing 
in an AT rule like

	div.special { ... }
	div.special * { ... }

The problem  would be solved. The !tie might be more elegant for 
simple cases but if we need an AT rule for complex cases in any case 
why not use it for everything?

The only problem is how can one implement this feature with high 
performance? I can see much use for this and if it slows down the 
rendering it might annoy the user.

Received on Monday, 5 January 2004 10:12:56 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:10 UTC