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

Trigger and Submit Control

Standard appearance

Usage

<xforms:trigger>
  <xforms:label>Browser Button</xforms:label>
</xforms:trigger>

Appearance

NOTE: Since 2011-10-06, standard CSS is applied to triggers and submit buttons to have a consistent appearance between browsers.

Minimal (link) appearance

Usage

<xforms:trigger appearance="minimal">
  <xforms:label>Link Button</xforms:label>
</xforms:trigger>

Appearance

Creating a button with embedded images and markup

[TODO]

Modal trigger and submit

Usually, activating a trigger or submit button on the client doesn't prevent further actions in the user interface. Sometimes however it is useful to block such actions until further processing is complete, for example calling a submission that saves a document.


You can obtain this behavior by using the xxforms:modal="true" attribute on <xforms:trigger> and <xforms:submit>:

<xforms:trigger xxforms:modal="true">
    <xforms:label>Save</xforms:label>
    <xforms:send ev:event="DOMActivate" submission="save-submission"/>
</xforms:trigger>

With this attribute set to true, user input is blocked until all the events triggered by DOMActivate are processed. In the meanwhile, the page is grayed out and an icon appears indicating that background processing is taking place.

As soon as users activate (press enter or click) on a modal trigger or submit, the corresponding button looses the focus. This prevents users from being able to press enter and thus activate a button which still has the focus, while screen is grayed out.