- From: Erik Bruchez <ebruchez@orbeon.com>
- Date: Thu, 3 Apr 2008 20:50:24 -0700
- To: www-html-editor@w3.org
All, We have this situation in XForms that the XForms document may refer to separate documents known as XForms instances. Those can be specified inline: <xforms:instance id="my-instance"> <my-data>...</my-data> </xforms:instance> or they can be loaded externally: <xforms:instance id="my-instance" src="http://example.org/ document.xml"/> or they can even be replaced at runtime through xforms:submissions. At any rate, instances are considered separate DOMs by the XForms processor. Therefore, one thing which we can't do at the moment is attaching event listeners in the XForms document to nodes in the instances, as attaching using the @observer attribute would refer to ids located in the XForms document, not ids in the instance. One useful case for this would be listening to DOM Mutation Events happening in an instance. It would be good if XML Events 2 proposed a solution to that problem, although a the moment I don't have a concrete proposal on the table. Best, -Erik -- Orbeon Forms - Web Forms for the Enterprise Done the Right Way http://www.orbeon.com/
Received on Friday, 4 April 2008 03:52:27 UTC