W3C home > Mailing lists > Public > www-style@w3.org > December 2008

Re: no-cascade proposition

From: Jordan Osete <jor@joozt.net>
Date: Thu, 11 Dec 2008 20:19:11 +0100
Message-ID: <494167AF.7030705@joozt.net>
To: www-style@w3.org

Hello,

Though the "no-cascade" problem is effectively hard to solve purely in 
CSS (namespacing or iframes seem the best way to me), the "no-inherit" 
one can be solved, as far as I can see, in a very straightforward 
manner. Some kind of property like "disable-inheritance" that would 
apply to an element, and simply allow to enable or disable the 
inheritance for this element.

    disable-inheritance: none | all;

The advantage of using "none" and "all" is that it could later be 
extended to a list of properties, if really needed.

Regards,
Jordan Osete

Boris Zbarsky a écrit :
>
> Niels Matthijs wrote:
>> Well yeah, but I don't think it's appropriate to fix stuff at html
>> level just because it gives you problems on css level?
>
> Your issue is that some of your HTML elements differ from others in an 
> important way. You need to communicate that to CSS somehow.  How do 
> you propose to do this?
>
>> Furthermore,
>> there are problems with iframes adapting to the height of the
>> included code.
>
> Please go read up on seamless iframes.  Though arbitrary cross-site 
> inclusion won't allow auto-height-sizing, it will probably be allowed 
> with the appropriate Access-Control headers.
>
>> And I don't see why I should always include external
>> code through an iframe.
>
> Because you don't want it to pollute your script scope (or vice 
> versa), just like you don't want CSS rules to leak across the boundary 
> (in either direction)?
>
> -Boris
>
>
Received on Thursday, 11 December 2008 19:19:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:55:17 GMT