W3C

- DRAFT -

XForms Users Community Group Teleconference

24 May 2017

Agenda

See also: IRC log

Attendees

Present
Alain, Erik, Philip, Steven
Regrets
Chair
Steven
Scribe
Steven

Contents


ACTION-2122: Update the spec @incremental text

https://lists.w3.org/Archives/Public/public-xformsusers/2017May/0018

Steven: I did this. Please check.

ACTION-2123: Update the control events as per the email

https://lists.w3.org/Archives/Public/public-xformsusers/2017May/0014

Steven: I did this too.
... please read carefully.

Events after xforms-disabled

https://lists.w3.org/Archives/Public/public-xformsusers/2017May/0030

Steven: Should events be targetted at disabled controls?

Erik: Two different philosophies
... they are still functioning at some level.
... In our implementation they don't receive events
... If it remains disabled, we don't dispatch events.

Steven: Listeners also get disabled

Erik: I believe so

<ebruchez> 5.3.5 The relevant Property

<ebruchez> "event handlers for events targeted to a non-relevant control are disabled"

https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_relevant_Property

Erik: Not sure if this is right...
... What about the case of submitting a disabled event to a control with a listener for that event...
... a corner case.
... Not sure why this is even in the spec.
... Doesn't seem very necessary.

Steven: We also have this in the spec:

"If a run-time element is destroyed, then any delayed events targeted at

that element are removed from the delayed event queue. A run-time element

may be destroyed for a number of reasons, such as removal of controls

associated by a repeat with an instance data node that is destroyed."

Steven: What happens when a delayed event dispatch is targetted at a disabled element

Erik: Also a corner case, but I can see how it could happen.

Steven: Do we just leave it as it is?

Erik: Ideally, xforms-disabled needs to be clarified.
... I don't see the need for disabling event handlers.
... There may have been a rationale.
... I should check what our implementation does.

<ebruchez> https://github.com/orbeon/orbeon-forms/issues/134

Erik: Oh I see a case, where events handlers are in a group that has become nonrelevant

Steven: But a group is a control, so it is just handled by the general case.
... Discuss next week.

ACTION-2124: Deprecate the refresh etc events

https://lists.w3.org/Archives/Public/public-xformsusers/2017May/0015

Include reset?

https://lists.w3.org/Archives/Public/public-xformsusers/2017May/0031

Steven: Done. But should reset be included in the deprecated list?
... Look at this table: https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Events

Erik: That's OK.

<ebruchez> We still cannot hear you.

I'll rejoin

Dispatch with delay="0"

https://lists.w3.org/Archives/Public/public-xformsusers/2017May/0034.html

Steven: So you mean you want to say "dispatch this event immediately after I've finished".

Erik: The spec says a delay of 0 means it is dispatched immediately.
... which means while the current heandler is running, the event is dispatched.

Alain: I always put an event on the queue, delay=0 or absent.

Steven: Do you have use case for dispatching immediately Erik?

Erik: Good question.
... I wonder what JS does.

<scribe> ACTION: Erik to check whether JS always queues events. [recorded in http://www.w3.org/2017/05/24-forms-minutes.html#action01]

<trackbot> Created ACTION-2125 - Check whether js always queues events. [on Erik Bruchez - due 2017-05-31].

Erik: So there is a question whether we need the use case to dispatch immediately
... there are small things in that text. What happens if delay="bar"

Steven: Right, in other cases, we don't dispatch.

Erik: The empty string would be OK, but not garbage

<scribe> ACTION: Steven to update dispatch text not to accept garbage for @delay [recorded in http://www.w3.org/2017/05/24-forms-minutes.html#action02]

<trackbot> Created ACTION-2126 - Update dispatch text not to accept garbage for @delay [on Steven Pemberton - due 2017-05-31].

AOB

[None]

[ADJOURN]

Summary of Action Items

[NEW] ACTION: Erik to check whether JS always queues events. [recorded in http://www.w3.org/2017/05/24-forms-minutes.html#action01]
[NEW] ACTION: Steven to update dispatch text not to accept garbage for @delay [recorded in http://www.w3.org/2017/05/24-forms-minutes.html#action02]
 

Summary of Resolutions

[End of minutes]

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

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)

Succeeded: s/;/:/
Succeeded: s/is reset/should reset be/
Present: Alain Erik Philip Steven
No ScribeNick specified.  Guessing ScribeNick: Steven
Inferring Scribes: Steven
Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2017May/0035
Found Date: 24 May 2017
Guessing minutes URL: http://www.w3.org/2017/05/24-forms-minutes.html
People with action items: erik steven

[End of scribe.perl diagnostic output]