Re: [CSS] Rules for parsing and compatibility

Svend Tofte wrote:

> Doesn't all of this, depend on yet again, the browser maker, to implement 
> properly? And worse yet, take a browser such as NS4, and see just how 
> inconsistent it's CSS support is, and I honestly can't imagine how it would 
> work. Does NS itself even know, just how spotty support it has?

Yes - that's the whole point. I don't understand what you're missing 
here. Browsers like NS4 would ignore the style specified in the 
'@tie' block just because it is unknown to it:

h1 { /* simpler style goes here */ }
@tie {
   h1 { /* advanced style goes here */ }
}

therefore will use only the style specified outside the '@tie' 
block. A modern UA on the other hand would know about the '@tie' 
block and will process it.

> Also, this would block a single rule, but how could one account for the 
> interaction between rules (for there is bound to be some)? Wrapping the 
> entire stylesheet in a @compat thing?

How exactly is best to process such blocks - we're about to clarify. 
Do only separate declaration blocks inside '@tie' should are 
invalidated or the whole '@tie' block? - your opinion is welcome.

>> Don't know if this has been already discussed and proposed but I 
>> remember reading about such issues couple of times. The thing is to 
>> address the different level of UAs support of the CSS spec and the 
>> new versions of it. So, if we have:
> 
> Interesting idea, but in general, I wonder if this is really the job of the 
> standards, to include methods for checking so fine grained support levels.

I think the method I'm suggesting here is really generic and simple 
and is very important for making accessible content on the web, so I 
think - this is really "a job of the CSS spec".

-- 
Stanimir

Received on Tuesday, 30 December 2003 09:43:00 UTC