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

RESOLVED FIXED

Status

()

Core
Disability Access APIs
RESOLVED FIXED
11 years ago
11 years ago

People

(Reporter: Joanmarie Diggs, Assigned: Aaron Leventhal)

Tracking

(Blocks: 2 bugs, {access})

Trunk
x86
Linux
access
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

11 years ago
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. :-)
(Assignee)

Updated

11 years ago
Blocks: 368875
(Assignee)

Comment 1

11 years ago
Created attachment 280649 [details] [diff] [review]
FireCurrentFocusEvent() synthesizes a focus event which unfortunately has no original target, so use passed-in target node in that case, which is correct anyway
Attachment #280649 - Flags: review?(Evan.Yan)

Updated

11 years ago
Attachment #280649 - Flags: review?(Evan.Yan) → review+
(Assignee)

Updated

11 years ago
Attachment #280649 - Flags: approval1.9?

Updated

11 years ago
Attachment #280649 - Flags: approval1.9? → approval1.9+
(Assignee)

Updated

11 years ago
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.