Comments? Feedback?

This wiki does not yet support public comments (a limitation of Google Sites), so we encourage you to post your comments either:

On Twitter by responding to @orbeon.

On our community mailing list: subscribe sending an email to ops-users-subscribe@ow2.org (content of subject/body doesn't matter), you'll get a response with the email to use to send your message to the community mailing list.

Recent site activity

Delayed Events

Support and limitations

Orbeon Forms partially supports the XForms 1.1 delay attribute on <xf:dispatch>. The limitations are:

  • A delay greater than zero always incurs a round-trip with the client. This may mean higher latency and ressource usage than could be expected. You are advised to use delays in the order of seconds at least.

  • Events are not combined as specified in XForms 1.1.

  • Custom event context information is not supported and simply ignored.

Extensions

The boolean xxf:show-progress attribute allows specifying whether the client must enable the loading indicator when sending back delay events from the client. The default is true and the indicator is used.

<xf:dispatch name="my-event" targetid="my-model" delay="2000"
  xxf:show-progress="false"/>

The xxf:progress-message attribute allows specifying a custom progress message when xxf:show-progress is true. By default, the standard progres message is used.

<xf:dispatch name="my-event" targetid="my-model" delay="2000"
  xxf:show-progress="true"
  xxf:progress-message="Autosave..."/>

For more information, please visit the XForms 1.1 specification.