W3C home > Mailing lists > Public > www-style@w3.org > November 2009

Re: [cssom] unrecognized rules and properties

From: Anne van Kesteren <annevk@opera.com>
Date: Mon, 30 Nov 2009 09:27:46 +0100
To: "Mike Wilson" <mikewse@hotmail.com>, www-style@w3.org
Message-ID: <op.u368gk1d64w2qv@anne-van-kesterens-macbook.local>
On Tue, 24 Nov 2009 09:43:24 +0100, Mike Wilson <mikewse@hotmail.com>  
> One may choose to apply grammars at different levels of
> detail, so I'm not entirely sure what is the specific problem.
> Have there been changes in these areas since the last CSSOM
> spec? (sorry if this is obvious, haven't been following)

To answer this question specifically. The last CSSOM draft defined almost  
nothing in detail. Especially when it comes to string representation of  
CSS constructs. All it said about CSSUnknownRule was "The CSSUnknownRule  
interface represents an at-rule not supported by this user agent."  
Considering that the CSS parsing specification dicates throwing away  
everything you do not recognize without defining implementation details as  
to what should be thrown away etc. this is highly unuseful.

You mention preserving unrecognized properties as well and presumably  
other constructs than unrecognized at-rules too? It's not all clear to me  
how all that could work nicely, but maybe you can convince an implementor  
to put some thought into it.

Personally I hope XBL will be able to solve the primary use case you  
mention. I.e. providing a shorthand (a binding in the case of XBL) for  
custom implemented look and feel.

Anne van Kesteren
Received on Monday, 30 November 2009 08:28:28 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:30 UTC