overwrite-file-dialog
).<fr:label>
and <fr:message>
.<fr:negative-choice>
and <fr:positive-choice>
elements to indicate which buttons you want to have, and in which order they should be shown.<fr:positive-choice``>
, which will run when/if users press the Yes button.fr-show
to the dialog:<fr:label>
inside the button element. For instance, you would change the label for positive choice from Yes to OK and for the negative choice from No to Cancel with:<xhtml:span>
with the class indicated in the table below around each button, which allows you to have a different style depending on the button type. For instance, if you can use the following CSS rule to remove the icon for the positive choice button:<fr:positive-choice>
xbl-fr-alert-dialog-positive
<fr:negative-choice>
xbl-fr-alert-dialog-negative
<fr:neutral-choice>
xbl-fr-alert-dialog-neutral
<fr:``positive-choice``>
or or , and run them on the DOMActivate
event, as done in the example above.positive-targetid
, negative-targetid
, or neutral-targetid
. Then, the alert dialog dispatches an event named fr-positive
, or fr-negative
, or fr-neutral
to that element. This second technique is particularly useful when you want to have one instance of an alert dialog that you want to reuse from the multiple places in your form.context
; the value of this property must be a string, and it will be passed back to your handler for fr-positive
, or fr-negative
, or fr-neutral
. This is particularly useful when you want to "forward" an event property to your custom handler. For instance you can open the dialog with:xxf:context
instead of xf:property
.fr:message
, you can pass it dynamically when opening the dialog:xxf:context
instead of xf:property
.xbl-fr-alert-dialog-question
and the dialog looks like:xbl-fr-alert-dialog-info
and the dialog looks like: