It was related with focus handling in dialogs where we get focus event for document and then for focused element. Nowdays this code makes us to fire a11y focus event for focused element twice. That's not necessary any more since we coalesce focus events from the same document and in other words we fire a11y focus event for focused element. I don't like current approach since it's timing related and may result in twiced a11y focus events what's not necessary.

I'd like our guru to take a try build for a spin here.

(In reply to comment #1) > I'd like our guru to take a try build for a spin here. This one contains all my latest patches: http://ftp.mozilla.org/pub/mozilla.org/firefox/tryserver-builds/surkov.alexander@gmail.com-02c4399322f7

I just ran with this build, and cannot report anything wrong with it. It reports focus fine when switching from one app to another or when switching tabs. I also tested with both NVDA and JAWS to make sure.

Comment on attachment 493685 [details] [diff] [review] patch r+a=me conditional on Marco's second spin working out ok.

Nope, there's something wrong when you go to www.youtube.com and JAWS running. The browser freezes either immediately, or after you enter a search term and press ENTER. It doesn't appear to hang taskmanager-wise, but JAWS doesn't read anything any more, no keyboard commands work etc.

try server build against trunk - http://ftp.mozilla.org/pub/mozilla.org/firefox/tryserver-builds/surkov.alexander@gmail.com-25bba87ca3ce

new try server build - http://ftp.mozilla.org/pub/mozilla.org/firefox/tryserver-builds/surkov.alexander@gmail.com-6f2e407b7f90

This latest try-server build works fine with JAWS and Youtube as well. I cannot reproduce the problems I describe in comment #5 with this build. So whatever finetuning you did seems to have solved this problem.

landed on 2.0 - http://hg.mozilla.org/mozilla-central/rev/dfedd535f514