Don't fire focus event for current focused accessible when document gets focus

RESOLVED FIXED in mozilla2.0b8



Disability Access APIs
7 years ago
7 years ago


(Reporter: surkov, Assigned: surkov)


(Blocks: 1 bug, {access})


Firefox Tracking Flags

(Not tracked)



(1 attachment)



7 years ago
Created attachment 493685 [details] [diff] [review]

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.
Attachment #493685 - Flags: review?(bolterbugz)
Attachment #493685 - Flags: approval2.0?
I'd like our guru to take a try build for a spin here.

Comment 2

7 years ago
(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:

Comment 3

7 years ago
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]

r+a=me conditional on Marco's second spin working out ok.
Attachment #493685 - Flags: review?(bolterbugz)
Attachment #493685 - Flags: review+
Attachment #493685 - Flags: approval2.0?
Attachment #493685 - Flags: approval2.0+

Comment 5

7 years ago
Nope, there's something wrong when you go to 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.

Comment 6

7 years ago
try server build against trunk -

Comment 7

7 years ago
new try server build -

Comment 8

7 years ago
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.

Comment 9

7 years ago
landed on 2.0 -
Last Resolved: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b8
You need to log in before you can comment on or make changes to this bug.