Re: question to implementors: handling of initial validation

Hi Joern,

For Mozilla we handle the states via the model object.  And we don't 
allow the state events (valid, invalid, readonly, etc) to be generated 
until after xforms-ready has been dispatched to that model.  So even 
though an alert will automatically handle the xforms-invalid, 
xforms-out-of-range and xforms-binding-exception events that its parent 
element can get, the element won't get the xforms-invalid or 
xforms-out-of-range events until after xforms-ready.

If you care to look at it, the code is here: 
http://lxr.mozilla.org/mozilla/source/extensions/xforms/nsXFormsModelElement.cpp#1139

--Aaron

Joern Turner wrote:
> 
> I'm wondering how other implementors handle the problem of NOT 
> displaying initial validation alerts.
> 
> It's a common problem of XForms authors that they don't like to puzzle 
> the user by showing a bunch of alerts before the user even had a chance 
> to put something into the fields (after init).
> 
> Joern
> 
>

Received on Thursday, 24 May 2007 20:36:44 UTC