*-error events default action

• From: Steven Pemberton <steven.pemberton@cwi.nl>
• Date: Sat, 16 Mar 2019 19:31:53 +0100
• To: " XForms" <public-xformsusers@w3.org>
• Message-ID: <op.zyrcffb3smjzpq@steven-xps>

https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Events

Most *-error events are fatal, with three exceptions:

   load-error
   output-error
   submit-error

which have no default action: they are notification events.

With the possible exception of output-error, I think this is wrong.

In particular with submit-error, if a submission goes wrong, nothing  
happens, and it's typically a pain to discover what has gone wrong.

I would like to agitate for a Warning classification, which requires an  
implementation to report the event but to allow processing to continue  
after the error. Something like this:

     <message level="modal" ev:event="xforms-submit-error">Submission  
error.
                      error-type: <output value="event('error-type')"/>
                      error-message: <output  
value="event('error-message')"/>
                      resource-uri: <output value="event('resource-uri')"/>
                      response-status-code: <output  
value="event('response-status-code')"/>
                      response-reason-phrase: <output  
value="event('response-reason-phrase')"/>
             </message>
Steven

Received on Saturday, 16 March 2019 18:32:19 UTC