Re: ACTION-2296: Add text to make it clear where xforms-action-error is dispatched to.

Summary.

The last decision we made was to leave <load/> as-is, except to dispatch 
xforms-load-error not to the <load/> but to the handler, in the same way as 
xforms-action-error is dispatched.
See https://www.w3.org/2021/01/29-forms-minutes#t03

Steven


On Friday 22 January 2021 14:39:09 (+01:00), Steven Pemberton wrote:

 > I expanded this action slightly to make sure that whenever the verb 
'dispatch' is used, that it is clear where the event is dispatched to.
 > I added a definition of 'observer' to the glossary.
 > Two questions arose, related to the idea "do not send events to 
actions".
 >
 > 1) xforms-load-error really ought to be an xforms-action-error with an 
error-type of "load-result" (or load-error?), which would solve the problem 
(alternative approach: if the result is empty, the action has no effect)
 >
 > 2) (I know this is not complete yet) The return element was dispatching 
xforms-action-element to itself. I have corrected this.
 >
 > Steven
 >
 > On Fri Jan 15 2021 16:08:05 GMT+0100 (Central European Standard Time), 
XForms Users Community Group Issue Tracker wrote:
 >
 > > ACTION-2296: Add text to make it clear where xforms-action-error is 
dispatched to.
 > >
 > > https://www.w3.org/2005/06/tracker/xforms/actions/2296
 > >
 > > Assigned to: Steven Pemberton
 > >
 > >
 > >
 > >
 > >
 > >
 > >
 > >
 > >

Received on Friday, 26 March 2021 13:47:49 UTC