This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25723 - [D3E]Case-sensitive or case-insensitive for getModifierState() method?
Summary: [D3E]Case-sensitive or case-insensitive for getModifierState() method?
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - DOM3 Events (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Gary Kacmarcik
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-15 09:02 UTC by Arkadiusz Michalski (Spirit)
Modified: 2014-05-21 01:19 UTC (History)
4 users (show)

See Also:

Attachments

Description Arkadiusz Michalski (Spirit) 2014-05-15 09:02:03 UTC 
What size characters should be valid in this method (for MouseEvent and  KeyboardEvent):

- case-sensitive (Firefox)
- case-insensitive (IE)

Chrome not support this method. Better specify this requirement explicitly in the specification.
Comment 1 Anne 2014-05-15 12:04:52 UTC 
Case-sensitive please. ASCII case-insensitive otherwise, but that's icky.
Comment 2 Anne 2014-05-15 12:07:49 UTC 
Also, this should be a enum, or at least have the same semantics, I suspect. Which also argues for it being case-sensitive.
Comment 3 Masayuki Nakano 2014-05-21 00:30:33 UTC 
I like case-sensitive because .key value is so.
Comment 4 Gary Kacmarcik 2014-05-21 01:19:38 UTC 
Agreed on case-sensitivity.

Fixed in ED: https://dvcs.w3.org/hg/dom3events/rev/14aad77c5c56