Hi Darin,
Erik suggested you might have some thoughts. In my proposed extension
api for accessibility (http://codereview.chromium.org/402099) one of
the functions is to simulate a key press. How should the client
express the key they would like to press? The current proposed
function prototype is:
{
"name": "simulateKeyPress",
"type": "function",
"description": "Simulate pressing a key.",
"parameters": [
{
"type": "object",
"name": "keyInfo",
"properties": {
"key": {"type": "integer", "description": "The code of
the key to press, corresponding to event.keyCode."},
"control": {"type": "boolean", "optional": true,
"description": "True if the control key is down."},
"shift": {"type": "boolean", "optional": true,
"description": "True if the shift key is down."},
"alt": {"type": "boolean", "optional": true,
"description": "True if the alt key is down."}
}
}
]
}
What do you think? Should the key be a keyCode? A charCode?
Should it be cross-platform, or should it match what would be returned
by an onKeyDown handler? Are those even mutually exclusive?
My current thinking is: the symmetry of using the same key codes
returned by onKeyDown is appealing. Also, even though there are some
differences, the most common keys needed to automate the UI (tab,
enter, arrows, alphanumerics) are already consistent across platforms.
Thanks,
- Dominic
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
