- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Thu, 14 Sep 2017 21:24:56 +0200
- To: "Erik Bruchez" <ebruchez@orbeon.com>
- Cc: XForms <public-xformsusers@w3.org>
Received on Thursday, 14 September 2017 19:25:24 UTC
On Thu, 14 Sep 2017 18:17:46 +0200, Erik Bruchez <ebruchez@orbeon.com> wrote: > What happens if you write: > > <setvalue ref="some-incorrect-expression" value="42"/> > > I imagine that the intent of `expression-error` would have been to > reflect that kind of error. Ah! I see now there is a note that suggests this, but it is not specified anywhere. I'll fix that. Steven > > On Thu, Sep 14, 2017 at 7:49 AM, Steven Pemberton > <steven.pemberton@cwi.nl> wrote: >> While working on the two error-type actions, I noticed this: >> >> https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_xforms-action-error_Event >> >> error-type string One of the following: >> expression-error, binding-error, script-error, script-language-error, >> other-error. >> >> However, I can find no place where expression-error, binding-error, or >> other-error are used. >> (There are however separate events for xforms-expression-error, >> xforms-binding-error.) >> >> Does anyone generate an xforms-action-error with any of these values? >> If not, I will remove them from the spec. >> >> Also, since the remaining two are new to this spec, I intend to remove >> the word "error" from the end, since it is redundant. >> >> Steven
Received on Thursday, 14 September 2017 19:25:24 UTC