* Jon Ferraiolo wrote: >But I would expect that the most common scenario will be that XBL widget >libraries will define widgets which expose methods and DOM attributes. (And >generate events.) If that is indeed the case, then saying "widgets which >expose interfaces cannot be bound with CSS" is not a good approach -- it >wouldn't be worth the effort. Just extend the sXBL matching which is based >on QName to an XPath expression which is evaluated at the time the custom >element is added to the document. If the XPath expression matches, then >turn the custom element's identity into what the binding defines. So @element should be renamed to something less restrictive like @match? -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/Received on Thursday, 24 March 2005 00:16:20 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 4 September 2006 18:11:33 GMT