XFA Specification
Chapter 15, Template Specification
Template Reference
502
The event element
An automation element that causes a script to be executed or data to be submitted whenever a particular
event occurs.
<event
Properties:
activity="click
|
initialize
|
enter
|
exit
|
mouseEnter
|
mouseExit
|
change
|
preSave
|
postSave
|
prePrint
|
postPrint
|
ready
|
docReady
|
docClose
|
mouseUp
|
mouseDown
|
full
|
preSubmit
|
preExecute
|
postExecute
|
preOpen"
id="xml-id"
name="xml-id"
ref="$
|
cdata"
use="cdata"
usehref="cdata"
>
<extras>
[0..1]
One-of properties:
<execute>
[0..1]
<script>
[0..1]
<signData>
[0..1]
<submit>
[0..1]
</event>
The event element is used within the following other elements:
exclGroup field proto subform
Any given object can only generate certain types of events. For example, a
subform
can generate
initialize
,
enter
, and
exit
events but it cannot generate events associated with key strokes and
mouse gestures because it cannot accept input focus. It is the responsibility of the template creator to
ensure that events are bound to appropriate objects.
The activity property
The name of the event. The accompanying
ref
property must specify an object that can generate the
named event.
change
Occurs when the user changes the field value. This will occur with each key-stroke, when text is
pasted, when a new choice is selected, when a check button is clicked, and so on.
click
Occurs when the user clicks in the field. Most systems define click as pressing and releasing the
mouse button while not moving the pointer beyond a very small threshold.