- From: Erik Bruchez <ebruchez@orbeon.com>
- Date: Tue, 23 Jun 2009 09:28:06 -0700
- To: xforms <www-forms@w3.org>
- Cc: Forms WG <public-forms@w3.org>
Joern, This does seem wrong. ev:event registers an action handler on the parent element (in the absence of an explicit ev:observer attribute). But the problem is that xforms:alert is not an action, and therefore it cannot run when the trigger is activated, or more generally if any DOMActivate event is dispatched to any of the xforms:trigger descendants. I cc the group on this so that this can be figured out. -Erik On Jun 23, 2009, at 1:24 AM, Joern Turner wrote: > The mentioned test cases all contain the following snippet: > > <xforms:trigger> > <xforms:label>Dispatch Alert Message</xforms:label> > <xforms:alert ev:event="DOMActivate" ref="/msg"></xforms:alert> > </xforms:trigger> > > In my understanding this is wrong cause the DOMActivate listener will > be attached to the trigger. The alert never will receive a > DOMActivate. I also can't find anything in the Spec saying that a > trigger must bring up its alert when activated. As a consequence this > test case can never be successful as it says: " When you activate the > Dispatch Alert Message trigger you must see a message that says > "Instance Alert Message". " > > Joern > -- Orbeon Forms - Web Forms for the Enterprise Done the Right Way http://www.orbeon.com/
Received on Tuesday, 23 June 2009 16:28:56 UTC