- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Thu, 01 Dec 2016 20:29:27 +0100
- To: "Erik Bruchez" <ebruchez@orbeon.com>
- Cc: XForms <public-xformsusers@w3.org>
- Message-ID: <op.yrs4fdxlsmjzpq@steven-aspire-s7>
Ah right, well spotted. Then you could use it like this.
<input ref="foo label="foo">
<action ev:event="xforms-value-changed" type="text/fortran">
WRITE (6, 601)
601 FORMAT("HELLO")
</action>
<action ev:event="xforms-action-error">
<message>Wrong action type</message>
</action>
</input>
Steven
On Thu, 01 Dec 2016 19:47:09 +0100, Erik Bruchez <ebruchez@orbeon.com>
wrote:
> "12.5.5 The xforms-action-error Event" [1] covers this:
>
> "Target: the event observer that caused the action to be executed"
>
> So it's the outer action element. Since the event bubbles you can listen
> to it anywhere in the enclosing scope.
>
> -Erik
>
> [1]
> https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_xforms-action-error_Event
>
> On Thu, Dec 1, 2016 at 5:45 AM, Steven Pemberton
> <steven.pemberton@cwi.nl> wrote:
>> https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_action_Element
>>
>> "If the type attribute is present, and the language it indicates is not
>> supported, then when the action element is activated, an
>> xforms-action->>error with error-type set to script-language-error is
>> dispatched. \"
>>
>> "If an error occurs during execution, an xforms-action-error with
>> error-type set to script-error is dispatched."
>>
>> Yes, but dispatched where? It can't be dispatched to the action element
>> itself I think, because it would be hard listening to errors going to
>> >>it.
>>
>> Steven
Received on Thursday, 1 December 2016 19:30:13 UTC