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

Re: dispatch with @delay question

From: Leigh L. Klotz, Jr. <Leigh.Klotz@Xerox.com>
Date: Thu, 18 Jun 2009 07:00:00 -0700
Message-ID: <4A3A4860.3040509@Xerox.com>
To: aaronr@us.ibm.com, www-forms@w3.org
Aaron,
We discussed this issue at our teleconference [1] and concluded [2] not 
to make any changes in the XForms recommendation.
However, we agree that no further events happen after model-destruct.

In other words, for an implementor, it's safe to assume that after 
model-destruct event dispatch is finished, no further delayed events 
should occur.

[1] 
http://lists.w3.org/Archives/Public/public-forms/2009Jun/att-0063/2009-06-17.html#topic5
[2] 
http://lists.w3.org/Archives/Public/public-forms/2009Jun/att-0063/2009-06-17.html#ACTION2

Leigh.

 >From: Aaron Reed <aaronr@us.ibm.com>
 >Date: Thu, 04 Jun 2009 16:21:07 -0500
 >To: www-forms@w3.org
 >Message-ID: <h09du1$a6h$1@ger.gmane.org>
 >
 >Hi,
 >
 >I didn't see this in the spec, but perhaps I missed it.
 >
 >I see in the spec rules like removing the event from the delay queue
 >before dispatching and if the target is deleted then the event should be
 >removed from the delay queue.  But I don't see anything in the spec that
 >mentions when all of the events in the delay queue should be destroyed.
 >  Should that happen as part of the xforms-model-destruct default
 >handling?  This seems like the type of thing that should be defined in
 >the spec if it isn't already.
 >
 >Thanks,
 >--Aaron
Received on Thursday, 18 June 2009 14:00:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:22:16 GMT