- From: John Boyer <boyerj@ca.ibm.com>
- Date: Mon, 27 Nov 2006 11:43:09 -0800
- To: www-forms@w3.org
- Message-ID: <OF1F09C263.0B85E9DB-ON88257233.0069FB35-88257233.006C51FC@ca.ibm.com>
In XForms 1.0 Second Edition, the itemset element was added to the list of targets for the xforms-select and xforms-deselect events. Well, it was not added everywhere e.g. in the event overview, so a correction is needed regardless of the outcome of the discussion. However, I believe it was an error to add itemset to the list of targets for these events. One does not select or deselect an itemset. It should be the case that the events are dispatched to the item elements in a select or select1, regardless of whether the item elements are declared in the source document or generated by an itemset. Although there is an ongoing problem nailing down the exact meaning of repeated content and how events flow between repeated content and the generating elements, it is still reasonable not to make itemset a target for these events because the content model for itemset allows actions such as those that would be handlers for xforms-select and xforms-deselect. By the same logic that allows us to duplicate the DOMActivate handler for a set of triggers created by a repeat, the actions in an itemset must be assumed to be duplicated into each generated item. Please send your thoughts on this topic. Thanks, John M. Boyer, Ph.D. STSM: Workplace Forms Architect and Researcher Co-Chair, W3C Forms Working Group Workplace, Portal and Collaboration Software IBM Victoria Software Lab E-Mail: boyerj@ca.ibm.com http://www.ibm.com/software/ Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Received on Monday, 27 November 2006 19:43:36 UTC