John Remmers wrote: > On Jun 18, 2007, at 11:29 AM, Larson, Timothy E. wrote: >> This is really a matter for Safari to work out. The accesskey modifier >> used by the browser should not be something that is used elsewhere in >> the system. The collision here is completely Safari's fault. If Cocoa >> uses Ctrl+letter already, then browsers should use Ctrl+Opt+letter, or >> Ctrl+Shift+letter, or whatever. The web page should be able to use any >> letter for an accesskey, trusting the browser not to cause confusion. > > Right. But the latest Camino and Firefox for OS X also set the > accesskey modifier to Ctrl and therefore have the same conflict as > Safari. At least for Camino and Firefox, one can modify this in user > preferences -- in "about:config", change the ui.key.contentAccess > value from 2 to 6 to make Ctrl+Opt the accesskey modifier. The only > solution for Safari that I've been able to find involves modifying the > WebKit source and rebuilding Safari (see http:// > www.macosxhints.com/article.php?story=200703171853311).
Personally, I was not aware of the emacs keybindings in Cocoa (I'd hazard a guess that most people are not) so perhaps the conflict is very limited in its scope of impact. Tim -- Tim Larson InterCall, a subsidiary of West Corporation Eschew obfuscation!
