14:59:51 RRSAgent has joined #forms 14:59:51 logging to http://www.w3.org/2013/06/26-forms-irc 14:59:53 RRSAgent, make logs public 14:59:53 Zakim has joined #forms 14:59:55 Zakim, this will be IA_XForms 14:59:55 ok, trackbot; I see IA_XForms()11:00AM scheduled to start in 1 minute 14:59:56 Meeting: Forms Working Group Teleconference 14:59:56 Date: 26 June 2013 15:00:06 CHAIR: Nick 15:00:42 zakim, code? 15:00:42 the conference code is 93676 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), nvdbleek 15:01:25 IA_XForms()11:00AM has now started 15:01:32 +nvdbleek 15:02:10 nvdbleek has changed the topic to: http://lists.w3.org/Archives/Public/public-forms/2013Jun/0018.html 15:02:14 Agenda: http://lists.w3.org/Archives/Public/public-forms/2013Jun/0018.html 15:02:14 +pfennell 15:02:26 +ebruchez 15:02:39 pfennell has joined #forms 15:03:11 +[IPcaller] 15:03:12 Scribe: Nick 15:03:26 zakim, I am [IPcaller] 15:03:26 ok, alain, I now associate you with [IPcaller] 15:03:36 Regrets: Steven, Uli 15:03:54 Agenda: http://lists.w3.org/Archives/Public/public-forms/2013Jun/0018.html 15:04:13 Topic: Dialog module 15:04:14 http://lists.w3.org/Archives/Public/public-forms/2013Jun/0015.html 15:04:34 nvdbleek: Had anybody time to review it already? 15:04:50 ebruchez: I send in some comments 15:05:21 ebruchez: 1. The reference to Core Form Controls was in the source but didn't 15:05:22 show. I fixed it. 15:06:08 ebruchez: 2. "the IDREF may not uniquely identify the desired dialog if the 15:06:08 dialog element bearing the matching ID resides in a repeating 15:06:09 construct such as element repeat" however we say the element is a 15:06:10 "top level container form control". 15:07:05 ebruchez: We talk about the ID resolution, but it needs to be a top level element 15:07:23 ebruchez: So we shouldn't talk about ID resolution 15:08:52 ACTION nvdbleek Remove note about ID resolution in show/hide elements because it is not needed the dialog element is a top level element 15:08:52 Created ACTION-1952 - Remove note about ID resolution in show/hide elements because it is not needed the dialog element is a top level element [on Nick Van Den Bleeken - due 2013-07-03]. 15:09:11 ebruchez: 3. Since `xf:dialog` is new, do we want to support `xf:show/xf:dialog`, since we have AVTs? 15:10:17 ebruchez: We are deprecating child elements, so we shouldn't add xf:dialog child elements for show/hide elements 15:10:50 ACTION nvdbleek remove dialog child element for show/hide element 15:10:50 Created ACTION-1953 - Remove dialog child element for show/hide element [on Nick Van Den Bleeken - due 2013-07-03]. 15:11:09 ebruchez: 4. It would be convenient if `xf:dialog/@dialog` was indeed optional, but would resolve, when possible, to the enclosing dialog. 15:11:52 ebruchez: the attribute is optional because it also supported the dialog child element 15:12:34 ebruchez: We could make the dialog attribute optional on the hide to hide the parent dialog element 15:13:36 nvdbleek: I'm note sure because it makes no sense on the show action 15:14:30 ebruchez: We don't this for recalculate either 15:14:45 ebruchez: (to specify the model, the model is mandatory) 15:15:08 nvdbleek: ebruchez would you like to be dialog optional on hide 15:15:45 ebruchez: It would be convenient, but it is not symmetrical 15:15:57 ebruchez: Let's wait a bit for this one 15:16:03 ebruchez: I know it is a use case 15:16:42 ebruchez: I'm rather in favour of making dialog attribute optional on hide 15:17:08 ebruchez: It is similar to the toggle action 15:18:40 but the toggle action is more like xf:show, so that's not helping 15:18:50 nvdbleek: I'm not sure, but on the other hand who will omit the dialog attribute on show 15:19:12 ebruchez: 5. Minor edits. [1] I wanted to do more, but some of the funny wording is used by group and switch too. I think readers are familar with the notion of a dialog, so I simplified a bit. 15:20:28 ebruchez: It is weird, but the wording is used other group controls too 15:21:29 ebruchez: 6. I had suggested `xforms-dialog-shown` and `xforms-dialog-hidden` as notification event names [3]. Right now, the text has `xforms-dialog-show` and `xforms-dialog-hide` as events dispatched by the action. One issue is: what happens with the dialog's "hide" button when present? There has to be a way to know that the dialog was hidden. Should we say that the button dispatches `xforms-dialog-show`? And/or should we have both show/hide and shown/[CUT] 15:21:29 one being the event for the action, the other one the event dispatched to the dialog when it is effectively opening/closing? 15:21:41 ebruchez: There are two type of events: 15:22:01 ebruchez: 1) dispatched by the action to open and close dialogs by the action 15:23:03 ebruchez: 2) Notification events (to know when a dialog is opened or about to be closed) 15:23:26 ebruchez: With the notification events you can for example copy some data 15:24:38 ebruchez: I suggested notification elements 15:25:31 ebruchez: The current events are cancellable so you can't listen for the events to be sure if the dialog is opened/closed 15:25:52 nvdbleek: I think we need the notification events 15:26:33 ebruchez: In our implementation the events aren't cancellable 15:27:42 nvdbleek: Doesn't it makes sense to be able to cancel the hide event (e.g.: prevent the dialog from disappearing till a certain condition is met) 15:29:07 ebruchez: It would be weird if you have a close button on your dialog and hitting it won't close the dialog 15:29:29 ebruchez: For switch it are notification events 15:30:25 ebruchez: I'm not convinced we need the actions to perform the action 15:30:43 ebruchez: The most versatile approach is to have 4 events 15:31:34 nvdbleek: Then xforms-dialog-hide will dispatch xforms-dialog-hiden in its default action 15:31:53 … xforms-dialog-show will dispatch xforms-dialog-shown in its default action 15:32:10 s/hiden/hidden 15:32:33 .. and xforms-dialog-hidden and xforms-dialog-shown are notification events (not cancellable) 15:34:03 ebruchez: You want the xforms-dialog-hidden event to be called just before it is hidden, otherwise the content won't be relevant 15:35:23 ebruchez: I will send a message to the group about this 15:36:15 ebruchez: 7. We had a question of what to do when the dialog becomes non-relevant, but I think that goes away as right now we say the dialog is only a top-level element. 15:37:34 nvdbleek: I'm quite sure there is no binding, we removed this quite some time ago 15:38:39 ebruchez: that's good for the dialog then 15:38:56 Topic: ACTION-1950 - Make @accept HTML compatible 15:38:57 http://lists.w3.org/Archives/Public/public-forms/2013Jun/0017.html 15:39:27 nvdbleek: I've reviewed the change, and I think it is OK 15:40:16 ebruchez: I pointed to the W3C version of HTML5 for the explanation of how to handle the accept attribute 15:40:42 alain: It's ok for me 15:40:49 Topic: Actions, and timeline 15:40:50 http://lists.w3.org/Archives/Public/public-forms/2013Jun/0010.html 15:41:25 nvdbleek: We discussed this last time 15:41:36 ebruchez: I have a few action items todo 15:43:04 -nvdbleek 15:43:05 -pfennell 15:43:06 -[IPcaller] 15:43:10 -ebruchez 15:43:12 IA_XForms()11:00AM has ended 15:43:12 Attendees were nvdbleek, pfennell, ebruchez, [IPcaller] 15:43:28 alain has left #forms 17:12:25 ebruchez has joined #forms 17:22:34 Zakim has left #forms 19:51:02 nvdbleek has joined #forms