See also: IRC log
<trackbot> Date: 25 July 2012
<scribe> Scribe: Steven
<nvdbleek> they have a Use Cases and Requirements
<nvdbleek> page at http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requirements
<nvdbleek> Schwerdtfeger, Richard
Steven: UI events are something we have been asking for a long time, and we created a first draft some time ago. I will dig it out.
Kurt: Anyone going to be there?
Steven: Yes, I'm talking
Kurt: See you there.
Erik: Some subtle issues with popup blockers
scribe: browsers try to identify popups that are a response to a click
Erik: It might not be reliable on some implementations
Steven: Is that reason to not include it in the spec?
Erik: Good question
... I think @target is a perfectly good use case. Clearly missing from XForms.
... it would be ideal to match it to @target from HTML
... It seems to be deprecated in HTML
Steven: No longer in HTML5
Kurt: That strengthens the argument that we should have it, on <submission>
<scribe> ACTION: Nick to add @target to submission [recorded in http://www.w3.org/2012/07/25-forms-minutes.html#action01]
<trackbot> Created ACTION-1909 - Add @target to submission [on Nick Van Den Bleeken - due 2012-08-01].
<nvdbleek> Orbeon has an extension event for this as erik pointed out http://wiki.orbeon.com/forms/doc/developer-guide/xforms-events#TOC-xxforms-index-changed
Erik: We have it; rarely useful,
but occasionally it is
... need to work out when it is sent
Steven: So we have two identified implementations; sounds like it is worth adopting
Nick: You dispatch it only when the value of the index changes, but not when the content under the index changes
Erik: Yes; we have other events
as well for the other cases
... it's just looking at the index value
... we have an event that says whether the nodeset of a repeat has changed
Steven: Are those events just as needed?
Erik: We did have a use
... It's a narrow use case, but we did need it.
Nick: If you really need to track
a repeat we need more events
... I think even value-changed is unreliable
Steven: How so?
Nick: Not always sent.
Erik: And it may be sent if the values do not change from the user's perspective.
Steven: So it is a case of over-specification? We should specify it by intent, not algorithmically.
Erik: We never reached closure on it
Nick: It was about relevance and
... some people wanted to combine all the events into one event
Erik: We agreed that controls
should be in charge
... but not about the little details
Steven: So should we reopen that?
Erik: We should, but it is not necessary for the repeat events
<scribe> ACTION: Steven to link errata document to wiki errata page [recorded in http://www.w3.org/2012/07/25-forms-minutes.html#action02]
<trackbot> Created ACTION-1910 - Link errata document to wiki errata page [on Steven Pemberton - due 2012-08-01].
Steven: Did you already do this Nick?
Nick: Not sure. I need to check.
Steven: I'll keep it on the agenda
<scribe> ACTION: Steven to dig out old intent-based events draft [recorded in http://www.w3.org/2012/07/25-forms-minutes.html#action03]
<trackbot> Created ACTION-1911 - Dig out old intent-based events draft [on Steven Pemberton - due 2012-08-01].
This is scribe.perl Revision: 1.136 of Date: 2011/05/12 12:01:43 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/... // Succeeded: s/TH/Th/ Succeeded: s/pops/popups/ Succeeded: s/issus/issues/ Succeeded: s/pops/popups/ Succeeded: s/pops/popups/ Found Scribe: Steven Inferring ScribeNick: Steven Default Present: Steven, Nick, +1.443.837.aaaa, Kurt Present: Steven Nick +1.443.837.aaaa Kurt Erik Regrets: Philip Agenda: http://lists.w3.org/Archives/Public/public-forms/2012Jul/0010.html Found Date: 25 Jul 2012 Guessing minutes URL: http://www.w3.org/2012/07/25-forms-minutes.html People with action items: nick steven[End of scribe.perl diagnostic output]