394547 - Giving focus to a tree in an autocomplete causes absence of future caret-moved events for the entry

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect)

Description

[Joanmarie Diggs]

Steps to reproduce:

1. Launch Accerciser and turn on event monitoring

2. Launch Firefox, move focus to the Location autocomplete and type something (e.g. "google")

3. Use left and right arrow to move among the characters typed.

4. Press down arrow to expand the autocomplete.  Then use down and up arrow to move among the items.

5. Press left arrow to once again move among the characters in the entry.

Expected results:  After step 5, caret-moved events would be emitted just as they were after step 3.

Actual results:  After step 5, caret-moved events are no longer emitted.

Additional notes:  

1. It is not necessary for the entry to be part of an official autocomplete.  The same results can be seen in the search entry on google.com.

2. In order to determine if this was a regression or simply something we hadn't noticed, I tried earlier builds.  After going as far back as the 3rd June build and finding the bug present, I stopped looking.  If it's a regression, it's not a recent one. :-)

Comment 1

[Aaron Leventhal]

Attachment: FireCurrentFocusEvent() synthesizes a focus event which unfortunately has no original target, so use passed-in target node in that case, which is correct anyway