W3C

- DRAFT -

XForms Users Community Group Teleconference

17 Jan 2018

Agenda

Attendees

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

Contents


Test Suite 2.0

https://lists.w3.org/Archives/Public/public-xformsusers/2017Nov/0016

Steven: Working on it, but nothing new to see this week

ACTION-2143: Spec up adding help hint alert and label to the model

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

Steven: All done. Please review.

9.7 The trigger Element

https://lists.w3.org/Archives/Public/public-xformsusers/2018Jan/0000.html

Steven: The implementations differ from the spec, so we need to change something.
... Presumably adding something to the spec.
... My feeling is that 'readonly' doesn't mean 'disable the trigger' semantically.

Erik: Trigger is a bit different from other controls, because it doesn't use the value.
... output may be similar.
... readonly is a little bit of s tretch.
... I presented the resoning in my email.
... It's the best we had.
... I never felt the need to do validity in the same way
... it never felt urgent to look at required or valid
... submit and trigger and different things.
... So I'm not entirely happy with using 'readonly', it was a practical solution
... I'm not entirely sure we need to use validity.

Philip: I agree with your logic Steven, I guess the reason why we have the problem is that if it is down to validity as one example, that validity affects the button or not.
... Isn't a case of not changing which MIP to use, but to say we're changing the appearance?
... I understand your idea, but my suggestion is to add something to a trigger.

Steven: Currently you can do this

<instance> <ok/></instance>

<bind ref="ok" readonly="valid(instance('data')/value)"/>

<trigger ref="ok"/>

Erik: I thought Philip's suggestion was to do something with @appearance
... but this would change how @appearance works
... and @appearance doesn't doesn't affect behaviour

Steven: Agreed
... For now, I'll add it to the spec, but with a note asking for feedback.

Alain: I will experiment with disabling on validity as well.

<scribe> ACTION: Steven to add readonly condition for trigger to spec with note asking for feedback.

<trackbot> Created ACTION-2154 - Add readonly condition for trigger to spec with note asking for feedback. [on Steven Pemberton - due 2018-01-24].

AOB

[None]

[Adjourn]

Summary of Action Items

[NEW] ACTION: Steven to add readonly condition for trigger to spec with note asking for feedback.
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/01/17 14:36:25 $

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/bin/bind/
Succeeded: s/gg//
Succeeded: s/Adourn/Adjourn/
Succeeded: s/Areed/Agreed/
Succeeded: s/SO/So/
Present: Alain Erik Philip Steven
No ScribeNick specified.  Guessing ScribeNick: Steven
Inferring Scribes: Steven
Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2018Jan/0008
Found Date: 17 Jan 2018
People with action items: steven

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]