Re: [XBL] multiple template, handlers, implementation elements

[Cyril Concolato]

Ian Hickson a écrit : On Wed, 6 Dec 2006, Cyril Concolato wrote: In Section 5 "Shadow Content", what is the purpose of allowing multiple template elements in a binding element if only the first one is used ? Multiple <template> elements are not allowed in a <binding> element. Section 2.2 is clear about this -- it says "Expected children: template: zero or one". Then there is a problem in the spec (references are from the editor's draft): section 4: "The template element used to generate a binding is always the first such element in a binding element. If the binding element is mutated in a way which changes which template element is the first, then the corresponding shadow tree must be regenerated." Remove the sentences. section 4.1: "Otherwise, its first template element must be deeply cloned." Remove 'first'. Similarly, in Section 6.4 why allowing several implementation elements in the binding if only the first one is used? or in Section 7.1, several handlers elements in the binding if only the first one is used? Again, all of those are only allowed to be present once. See section 2.2. See section 5.4 "The first implementation element child of the binding element must have its code compiled and run (see below)." See section 6.1: "the user agent must also invoke any appropriate event listeners attached to the binding's first handlers element." "All event handlers registered on the first handlers element of the binding are considered" There may be other that I missed. Cyril