XForms Users Community Group Teleconference

31 May 2017


See also: IRC log


Erik, Philip, Steven


ACTION-2126: Update dispatch text not to accept garbage for @delay


Steven: Please check the text

Dispatch with delay="0"



Steven: Two parts, one is Erik's reply about JS

Erik: You can dispatch events synchronously in JS

Steven: So that answered the question we had last week

Erik: Had it not been the case, we should have done asynch events only
... we don't say in the spec whether dispatch should be able to do synchronous events

Steven: So your suggestion is that no @delay or delay="" is synchronous, and delay="0" is asynchronous

Erik: We should clarify that.

Steven: We should check that Alain is happy with that, since he said last week that his events were always asynch

<scribe> ACTION: Steven to tighten wording about effect of @delay on <dispatch/> [recorded in http://www.w3.org/2017/05/31-forms-minutes.html#action01]

<trackbot> Created ACTION-2127 - Tighten wording about effect of @delay on <dispatch/> [on Steven Pemberton - due 2017-06-07].

Steven: I will also explicitly check with Alain.

Events after xforms-disabled


Steven: Related.
... How to ensure that the controls get the event before the handlers are disabled (and vice versa).
... How about sending the disabled event synchronously.

Erik: Maybe a bit tricky
... the problem is that we are in the middle of refresh; it was nice that the refresh was atomic

Steven: I understand that; it's just how to ensure that the control receives its disabled event before it is disabled

Erik: DOM doesn't have such a property of turning event listeners off

Steven: But SMIL does; in some ways it is a problem with the design of the DOM

Erik: I'm not sure we need to define anything actually
... an exception might be DOMActivate
... if an action dispatches to a disabled element, maybe you wouldn't want it to be activated

Steven: It sounds like we need to do a bit more thinking, because I don't see a solution yet, except to leave it sort of vague as it is now in the spec.
... Do you disable listeners in a disabled control?

Erik: Need to check, but I don't think so.

Steven: At present undecided.

Serialization as multipart/related


Steven: I had an action item to spec up <part/>
... which I have now started
... it turns out to be stickier than I had expected,
... hopefully ready by next week.




Summary of Action Items

[NEW] ACTION: Steven to tighten wording about effect of @delay on <dispatch/> [recorded in http://www.w3.org/2017/05/31-forms-minutes.html#action01]

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2017/05/31 13:24:37 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: Erik Philip Steven
Regrets: Alain
No ScribeNick specified.  Guessing ScribeNick: Steven
Inferring Scribes: Steven
Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2017May/0045
Found Date: 31 May 2017
Guessing minutes URL: http://www.w3.org/2017/05/31-forms-minutes.html
People with action items: steven

[End of scribe.perl diagnostic output]