W3C home > Mailing lists > Public > public-forms@w3.org > May 2008

Re: Question about nested XForms actions and ev:observer

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Sat, 17 May 2008 11:47:27 -0700
Message-Id: <4527E005-6699-47F6-B4EC-BA96D9D0ACDB@orbeon.com>
To: "public-forms (new)" <public-forms@w3.org>, www-html-editor@w3.org

John,

That sounds reasonable. Is it correct to say that, assuming XHTML 
+XForms, the ev:* attributes are expected to be *always* honored on  
XForms action elements, *except* if they are present on elements  
within inline instances?

-Erik

On May 16, 2008, at 4:48 PM, John Boyer wrote:

>
> Hi Erik,
>
> Yes, the inner action can have event attributes on it, yes they will  
> set it up as handler, and yes the inner action still does run as  
> part of the outer action even if it has event attribute on it.
>
> The same set of statements would be true of XML events elements were  
> used to remotely refer to the inner action and set it up as a  
> handler for events.
>
> When the so-called inner action is directly invoked to handle the  
> event for which it is directly registered, it is not considered to  
> be an "inner handler" just because it is inside of another xforms  
> action.  Specifically, it will execute deferred updates when  
> finished if it was directly invoked.  It only continues to defer  
> updates if it is executed by the outer handler.
>
> Cheers,
> John M. Boyer, Ph.D.
> Senior Technical Staff Member
> Lotus Forms Architect and Researcher
> Chair, W3C Forms Working Group
> Workplace, Portal and Collaboration Software
> IBM Victoria Software Lab
> E-Mail: boyerj@ca.ibm.com
>
> Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
> Blog RSS feed: http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw
>
>
>
>
> Erik Bruchez <ebruchez@orbeon.com>
> Sent by: public-forms-request@w3.org
> 05/16/2008 04:32 PM
>
> To
> "public-forms (new)" <public-forms@w3.org>
> cc
> www-html-editor@w3.org
> Subject
> Question about nested XForms actions and ev:observer
>
>
>
>
>
>
> All,
>
> Consider the following submission, located in a proper place so that
> the outermost <xforms:action> element can react to a DOMActivate  
> event:
>
> <xforms:action ev:event="DOMActivate">
>     <xforms:send submission="my-submission"/>
>     <xforms:action ev:event="xforms-submit" ev:observer="my-
> submission">
>         ...
>     </xforms:action>
>     <xforms:action ev:event="xforms-submit-done" ev:observer="my-
> submission">
>         ...
>     </xforms:action>
> </xforms:action>
>
> A few questions:
>
> * Is it legal for the nested actions to have ev:event and ev:observer
> attributes?
>
> * If so, do the nested <xforms:action> element actually register as
> event handlers on the specified observers?
>
> * Are those executed in the flow of the outermost action, if that
> action is triggered?
>
> -Erik
>
> PS: Clearly, I could write these actions as follows:
>
> <xforms:action ev:event="DOMActivate">
>     <xforms:send submission="my-submission"/>
> </xforms:action>
> <xforms:action ev:event="xforms-submit" ev:observer="my-submission">
>     ...
> </xforms:action>
> <xforms:action ev:event="xforms-submit-done" ev:observer="my-
> submission">
>     ...
> </xforms:action>
>
> But still, bear with me and assume I want to do the nesting, for the
> sake of seeing these questions answered ;-)
>
> --
> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> http://www.orbeon.com/
>
>
>

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/
Received on Saturday, 17 May 2008 18:48:23 UTC

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