Search and Top Navigation
#6218 closed bug (duplicate)
Opened October 22, 2010 08:31PM UTC
Closed February 20, 2011 02:03PM UTC
Last modified February 20, 2011 02:03PM UTC
Autocomplete with scroll behaves incorrectly with combination of mouse and keyboard user input
| Reported by: | yeoldeape | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.9.0 |
| Component: | ui.autocomplete | Version: | 1.8.5 |
| Keywords: | UI Autocomplete Mouse Keyboard Scroll | Cc: | |
| Blocked by: | Blocking: |
Description
Hi everybody,
This behavior can be seen on the demo posted on the jquery UI site:
http://jqueryui.com/demos/autocomplete/#maxheight
If the user mouses over one of the items and leaves it there, and then subsequently uses the keyboard to scroll down, the presence of the mouse seems to be firing an event which causes the selection to be higher in the list than expected.
This is also the case if the mouse happens to be positioned underneath the input box (where the autocomplete UL will be placed) before any input is actually entered (which can happen randomly even if the user is using only the keyboard). So it's really a critical issue for the "scrollable results" application, though of course that's only one application of the UI autocomplete element.
This behavior is seen using Safari Version 5.0.1 (5533.17.8) and Firefox/3.5.11 on Mac OS X 10.5.
Thanks,
Greg
Attachments (0)
Change History (4)
Changed October 25, 2010 01:47PM UTC by comment:1
| milestone: | TBD → 1.9 |
|---|---|
| priority: | critical → minor |
Changed February 20, 2011 02:02PM UTC by comment:2
See also here: http://bugs.jqueryui.com/ticket/7024
Changed February 20, 2011 02:03PM UTC by comment:3
| resolution: | → duplicate |
|---|---|
| status: | new → closed |
Closing as duplicate of a newer ticket because the newer ticket is more general and suggests a solution.
This is not critical, even for scrollable results. It's wrong and annoying, but doesn't prevent the use of the plugin at all. I'm also not sure that this can be cleanly fixed, since the browser is sending mouse events on scroll.