W3C home > Mailing lists > Public > public-forms@w3.org > June 2009

Re: Problem with Test Cases 8.2.4.a, 8.2.4.b, 8.2.4.c

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Tue, 23 Jun 2009 09:28:06 -0700
Cc: Forms WG <public-forms@w3.org>
Message-Id: <C0B678FD-60E5-46BF-8DBB-DB788147B995@orbeon.com>
To: xforms <www-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
> &quot;Instance Alert Message&quot;. "
>
> 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

This archive was generated by hypermail 2.3.1 : Tuesday, 1 October 2013 22:06:51 UTC