Steven Pemberton, HTML WG Chair
(The numbers in brackets refers to the identification number in the tracking system)
It would be wrong to rename the observer attribute to 'target', because observer and target are two different concepts, and many things would break if you only listened on the target.
It would be possible to eliminate the target attribute (and retain the observer attribute), but there are cases where it is useful to specify the target as well.
Agree. We have removed references to Qnames..
We have added a mention at the appropriate place. Done.
Agree. We now do not list them, but refer directly to the DOM2 Events spec for names and semantics. Done
Agree. See above.
No. 'Handler' should be able to reference an external handler. We don't define (in this spec) what it points to, to allow for maximum flexibility. A future companion spec will define options for handlers.
Agree. However, we are awaiting Modularization in Schemas to advance before doing this, so a schema will be added later.
We were planning on doing that, but a registration for ecmascript is not yet available.
This is true. There is nothing we can do about it however. It is an architectural problem of XML. We assume the User Agent can identify the elements.
We don't agree that this is implied by the text. It is certainly not intended! The text has been modified accordingly.
Agree. Section 2.5 says this.
It is not a task of this specification to define actual event names. We have removed all names from the specification, and referred to the DOM2 specification that defines them. We agree that this should be fixed, but not in XML Events.
Thank you, all changes have been made.
This is in progress.