I havenít tried this, yet, so Iím not sure it will work. Whatís interesting about Saxon-CE is that after the initial XSLT20Processor.updateHTMLDocument() is performed, the engine keeps running in the background waiting to handle events by performing transformations using the same XSL template identified initially. It also uses the same XML model initially. I doubt I can perform an identity transformation xdoc = XSLT20Processor.transformToDocument(xdoc) and expect this background engine to know that ixsl:source() has been updated without calling XSLT20Processor.updateHTMLDocument() to re-render the entire page. Thatís not very efficient.
Iím using contentEditable spans and the focus/blur events are not caught by Saxon-CE. I have JQuery code catching these events, but the XML variable Iíve been given is a stub and so I canít update the model directly. So now I will investigate whether I can write a transformation that updates the model correctly so that subsequent view transformations will see the update.
Eric, your presentation has provided good grist for the grinder, so to speak. Thanks for the post.