That commit fixes things for me... let's reopen if other problems show up.

Changes have been made in Git for this ticket:

Bug #9737: Fix accesskeys in Chrome/Mac on elements that are links

  1 files changed, 1 insertions(+), 1 deletions(-)
http://git.horde.org/horde-git/-/commit/0e7341cc7adbdf9d293f5e4735beed4c6874eaf5

On Linux and Windows, Chrome is triggering the default action of A 
tags when you fire an event manually. If you have an event handler 
registered on that element, the action is triggered twice, so you end 
up with two popups.
This is of course broken behavior and has security implications 
because it's an open field for click-hijacking.

This is the block that's triggering on Chrome 10/Mac causing the cases 
not to finish (if I comment out the return everything seems to work 
fine):

                 if (navigator.userAgent.indexOf('Chrome/') > -1 &&
                     elt.tagName == 'A') {
                     return;
                 }

What is that preventing in the versions you have?

They work fine in Chrome 8 on Linux and Chrome 10 on Windows. I don't 
have a Mac version that is supported by Chrome, so someone else need 
to take a look at those cases.

Your commit fixed things in DIMP, at least the common ones I use. On 
the test page, F, G, H, I, J, K, L, M all fail.

Changes have been made in Git for this ticket:

Fix access keys with Chrome on elements that are not links. Maybe 
fixes bug #9737?

  2 files changed, 9 insertions(+), 5 deletions(-)
http://git.horde.org/horde-git/-/commit/503221deb7286cf43637bd79e24845e7af38f20d

Please open /horde/js/accesskeys.html and test which cases don't work.

No accesskeys are working for me in DIMP; in Nag, they just focus the 
menu item, instead of activating it. No JS errors that I see. Cleared 
all cached static js files, etc.