Erik, we recognize the problem, but defer changes to MIP events for now because we need a broader based redesign of events for controls and possibly also for model. Regards, Ulrich Nicolas Lissé For the Forms WG > All, > > XForms 1.1 is much more specific than XForms 1.0 about sending MIP > events, in particular what events to send when controls become > relevant and non-relevant. This is good. The motivation for this was, > in my opinion, to make the MIP events actually useful, because they > now can be used to reliably track the status of controls. > > However, there is one hole: the spec does not mention that any MIP > events should be sent during XForms engine initialization. In > particular, there is no initial xforms-refresh, or otherwise > requirement that MIP events should be dispatched upon initialization. > > This means that it is currently not possible to determine the initial > status (in particular, validity) of the controls. > > This affects for example the use case of creating an error summary > that tracks the validity of controls in your page. > > I think that controls should initially dispatch MIP events so as to > make this use case possible. > > -Erik > > -- > Orbeon Forms - Web Forms for the Enterprise Done the Right Way > http://www.orbeon.com/ > >Received on Thursday, 13 September 2007 16:07:26 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 10 June 2009 18:12:16 GMT