- From: Ian Hickson <ian@hixie.ch>
- Date: Thu, 12 Oct 2006 01:04:57 +0000 (UTC)
- To: Matthew Raymond <mattraymond@earthlink.net>
- Cc: www-style@w3.org
On Wed, 11 Oct 2006, Matthew Raymond wrote: > Ian Hickson wrote: > > > > I wrote up a draft for a module that would define the 'binding' and > > ':bound-element' properties: > > > > http://dev.w3.org/cvsweb/~checkout~/2006/xbl2/css-module.html > > I'd like to see the value of "binding" as something like this: > > none | [ [ <uri> ] * <uri> ',' ]* <uri> Hm, that's a good point. I've changed it from accepting a comma-separated list to accepting a space-separated list. When we want to add fallback support, we can then use commas. Is that ok? I don't think we want to require fallback support at this early stage. It's probably better to keep things simple at the start. > The idea is that the property could support fallback like this: > > | binding: url("b1.xbl") url("b1.htc"), url("b2.xbl") url("b2.htc"); > > In the example above, if the user agent supports HTML Components, but > not XBL, then the user agent will bind "b1.htc" and "b2.htc" to the > selected elements. Without such fallback support, it's difficult to see > how this property can be considered neutral with regard to binding > languages. Well, IMHO you'd want the fallback at the outside for consistency with other such things in CSS, so it would look more like: binding: url("b1.xbl") url("b2.xbl"), url("b1.htc") url("b2.htc"); ...but I agree with the idea. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 12 October 2006 01:05:13 UTC