| 02:11 | <Krinkle> | Hm.. I'm trying to programmatically detect use of an accesskey="" trigger. |
| 02:11 | <Krinkle> | Looking at monitorEvents() in Chrome, I found I get two interesting events that differ from other types of button/link triggers |
| 02:12 | <Krinkle> | 1) A strange key value for the keydown event |
| 02:12 | <Krinkle> | 2) A click event with e.details = 0, and a non-null inputCapabilities. |
| 02:14 | <Krinkle> | But not sure if either of those is limited to accesskey triggers |
| 02:15 | <Krinkle> | The strange keydown event is limited to chrome ( key: "∆"), not in Safari. so that one falls off. |
| 02:15 | <Krinkle> | e.details = 0 seems cross-browser, but not sure if it's possible for other ways that can be zero for a non-regular click |
| 02:16 | <Krinkle> | sorry, meant a null sourceCapabilities. Normally for click events sourceCapabilities is an input capabiltities object |