At 04:16 PM 3/23/2005, Bjoern Hoehrmann wrote:
* 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?
Sounds like a good suggestion to me. I will forward this suggestion to the
XBL task force.
Jon
--
Björn Höhrmann · mailto:bjoern@xxxxxxxxxxxx · 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/
