Re: [uievents] Whethere KeyboardEvent.location depends on .code or .key? (#62)

@garykac I agree with .location depending on .key.

> The location attribute contains an indication of the location of the key on the device.

I think that this should be:

The location attribute contains an indication of the _logical_ location of the key. The value does not indicate the physical key position on the device. For example, if 'ControlLeft' key is mapped to different key, the value may not be DOM_KEY_LOCATION_LEFT. Similarly, if 'CapsLock' key is mapped to left 'Control' key, the value should be DOM_KEY_LOCATION_LEFT.

Or something similar.

And I found serious issue in next sentence:

> In case a DOM implementation wishes to provide a new location value, a value different from the defined constant values MUST be used.

The spec shouldn't allow this. For example, if a browser uses 0x04, UI Events spec won't add new constant value as 0x04... Any new value should be suggested to us. If you think there should be private used area, you should define the range like 0xF0000000 - 0xFFFFFFFF.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/62#issuecomment-161509392