RE: XML Events and XForms

Hi John,

> 2) Practically speaking, how is external access to the instance data
> provided?  Or is it internal to the XForms processor?

The getInstanceDocument() function in the model element.

> 3) The XML Events spec defines DOM mutation events for structure changes
> like insert or delete element as well as simple content changes like
> character data or attribute value changes.  Does this include changes
> made by XForms-specific actions like insert, delete and setvalue?

Actually, DOM level2 events defines the mutation events. Yes, if your instance data is based on a DOM implementation, these events
are thrown for every change.

> 4) XML Events defines many types of events.  With respect to listeners
> on instance data, I assume that only mutation events occur.  With
> respect to XForms UI, I assume that only user interface, mouse, key and
> mutation events occur (i.e. no HTML events).

That's what I assume, too.

> Why are there no 'key' events in XML events?  What is the per-keystroke
> event model for XForms?  And, if the user cuts or pastes text, what
> events occur?

No key events are fired. If incremental - attribute is set, then the value of an input can be updated in the instance for every
change (ie. keypress).

> 5) The mutation events are underspecified.  Does 'subtreeModified' fire
> for all ancestors of a changed, inserted or removed node?  Does
> characterDataModified fire on the text node that changes or its parent
> element?

As I recall, subtreeModified is sort of help-event, which you cannot count on firing at certain moment. Also, many changes will be
grouped to subtreeModified.

CharacterDataModified's target will be the text node. :

"The target of this event is the CharacterData node. "

see:
http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/events.html

-mikko

Received on Friday, 31 May 2002 08:03:49 UTC