I have found another issue with access-keys it seems.
This was originally found with the Wikipedia RichText editor WikEd. To reproduce try a rich text textarea (either wikEd on Wikipedia or use http://www.kevinroth.com/rte/demo.htm). Make sure the cursor is IN the textarea. Note that the textarea responds to ctrl-alt-* now. TextEdit also responds to these key combo's, so I'm guessing it's a left over from back then.
This is the 3rd set of accesskey's that running into a conflict situation. Perhaps a different approach is needed into solving this ? Perhaps something like what Opera has ? At least then I have visual feedback as to when my accesskey is working and when it is not. ~~~~
I don't understand this bug report. Could you please give precise steps to reproduce, together with expected results and actual results spelled out as clearly as possible (maybe with screenshots)?
Searching the page sources with Web Inspector, I don't see "accesskey" attribute anywhere.
From IRC discussion: apparently, the problem is that when Wikipedia editor is active, key combinations such as Ctrl+Option+I enter low ASCII characters instead of invoking access key actions. We need to confirm this and to make a reduction.
Bug 19820 could be the root cause.
The problem seems to be that iframes in WebKit do not inherit the container document's accesskeys as one would expect and how it works in Firefox as well as Internet Explorer (tested in most recent versions).
This problem still exists in Safari 9. Accesskey of a parent document, do not function if the focus is inside the child document.