W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2011

Minutes, 05 May 2011 DOM3 Events Telcon

From: Doug Schepers <schepers@w3.org>
Date: Wed, 11 May 2011 12:37:34 -0400
Message-ID: <4DCABB4E.4000805@w3.org>
To: "www-dom@w3.org" <www-dom@w3.org>
http://www.w3.org/2011/05/05-webapps-minutes.html

keyboard events

shepazu: I updated the spec based on hallword's (spelling?) notes

<jrossi> 
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#keys-keyCode-charCode-which

shepazu: added supplementary idl for charCode/keyCode/which
... there lots of legacy stuff we don't need to specify, but legacy 
keyboard events are mainstream
... not making it normative though
... it is not appendix because I wanted to keep it there near other 
keyboard stuff
... will change it to appendix

smaug: I'd suggest not using KeyboardEvent, but LegacyKeyboardEvent

jrossi: Why not switch to WebIDL?

shepazu: WebIDL is not stable enough yet

jrossi: about WDC vs D3E
... I have a testpage about that
... D3E doesn't need to restrict what the event type string can be

smaug: I agree
... the other difference is the exceptions from dispatchEvent

jrossi: I like keeping the two different exceptions

<jrossi> issue-178?

<trackbot> ISSUE-178 -- Implementations and DOM Core allow empty string 
and null event types -- raised

<trackbot> http://www.w3.org/2008/webapps/track/issues/178

resolution: accept the change request issue-178

<jrossi> issue-179?

<trackbot> ISSUE-179 -- DOM Core uses INVALID_STATE_ERR (DOMException) 
where D3E uses DISPATCH_REQUEST_ERR (EventException) -- raised

<trackbot> http://www.w3.org/2008/webapps/track/issues/179

resolution: it is useful to have separate exceptions for for different cases
Received on Wednesday, 11 May 2011 16:38:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:07 GMT