W3C home > Mailing lists > Public > public-webapi@w3.org > April 2006

DOM3EV: Specifying inappropriate modifiers to MouseEvent.initMouseEventNS

From: Cameron McCormack <cam@mcc.id.au>
Date: Thu, 20 Apr 2006 10:20:15 +1000
To: public-webapi@w3.org
Message-ID: <20060420002015.GE7322@port.mcc.id.au>

What should happen if a key that is not a modifier is given in the
modifiersList argument of the MouseEvent.initMouseEventNS method?  There
would be three such "not modifiers":

  1. keys that the implementation knows about and knows are not
     modifiers, such as "Tab" on a PC keyboard,

  2. those that the implementation knows about but also knows that the
     device doesn't support, such as "Shift" on a mobile phone, and

  3. those that the implementation does not know about, such as a
     "Hyper" key on a Sun keyboard, where the implementation has not
     been written with such a key in mind.

My initial reaction would be to do either:

  A. ignore (1) and store (2) and (3), or

  B. store (1), (2) and (3),

leaning towards B just because it's more easily implemented, and I can't
think of a valid reason for caring about whether "Tab" was specified as
a modifier or not, especially if there is no way to get the list of all
modifiers in effect.  I could imagine tiny implementations that would
want to avoid storing strings for modifier keys, and would favour just
storing (1) as a bitfield, but DOM 3 keyboard events are already pretty
string heavy.

 Cameron McCormack			ICQ: 26955922
 cam (at) mcc.id.au			MSN: cam (at) mcc.id.au
 http://mcc.id.au/			JBR: heycam (at) jabber.org
Received on Thursday, 20 April 2006 00:20:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:21 UTC