Bug Tracker

#2761 closed bug (invalid)

Opened April 29, 2008 05:47PM UTC

Closed June 10, 2009 09:16AM UTC

Last modified March 14, 2012 09:55PM UTC

[autocomplete] up/down arrow in list causes cursor to move in FF2 on a Mac

Reported by: zelph Owned by: joern
Priority: minor Milestone: 1.2.4
Component: plugin Version: 1.2.3
Keywords: autocomplete Cc:
Blocked by: Blocking:
Description

In FireFox 2.0 on a Mac, when you click up (or down) when there is a list showing the cursor moves to the front(back) of the input field. If for whatever reason the user wants to continue to type they are now at the start of the field instead of the end.

Steps to duplicate:

- In the "Single City" demo on the official page, type "saint".
- Press down one or more times, and then press up
- Type space or any additional character. They will be at the front of the string.

Expected result:

  • Typing should continue at the end of the string.
Attachments (0)
Change History (6)

Changed April 29, 2008 09:51PM UTC by joern comment:1

owner: → joern

Changed May 22, 2008 09:57AM UTC by joern comment:2

description: In FireFox 2.0 on a Mac, when you click up (or down) when there is a list showing the cursor moves to the front(back) of the input field. If for whatever reason the user wants to continue to type they are now at the start of the field instead of the end. \ \ Steps to duplicate: \ - In the "Single City" demo on the official page, type "saint". \ - Press down one or more times, and then press up \ - Type space or any additional character. They will be at the front of the string. \ \ Expected result: \ - Typing should continue at the end of the string. → In FireFox 2.0 on a Mac, when you click up (or down) when there is a list showing the cursor moves to the front(back) of the input field. If for whatever reason the user wants to continue to type they are now at the start of the field instead of the end. \ \ Steps to duplicate: \ {{{ \ - In the "Single City" demo on the official page, type "saint". \ - Press down one or more times, and then press up \ - Type space or any additional character. They will be at the front of the string. \ }}} \ \ Expected result: \ \ - Typing should continue at the end of the string.

Not sure yet whats causing this. For key up/down events, event.preventDefault() is called, well, to prevent the default. Can't reproduce it due to lack of a Mac.

Changed May 22, 2008 08:48PM UTC by aheimlich comment:3

Well, I can confirm that the issue exists. Unfortunately, I can't think of a fix for it, ATM :(.

Changed May 22, 2008 08:54PM UTC by aheimlich comment:4

Replying to [comment:3 aheimlich]:

Well, I can confirm that the issue exists. Unfortunately, I can't think of a fix for it, ATM :(.

I can also confirm that this issue is limited to Firefox 2 on Mac OS. Firefox 3 Beta 5 does not exhibit this issue, nor does Safari 3.1.1.

Changed June 02, 2008 10:23PM UTC by zelph comment:5

I tracked this down to be an issue with the autocomplete attribute that is set to off with the plugin. It does appear to be a browser bug as it can be duplicated with flat html input fields with and without the autocomplete attribute, so not much we can do about that.

I also confirm that it is fixed in FF3 RC 1.

Changed June 10, 2009 09:16AM UTC by joern comment:6

resolution: → invalid
status: new → closed

The autocomplete plugin is now developed under the jQuery UI umbrella. Reopen a ticket there (http://dev.jqueryui.com/) or participate on the planning wiki (http://wiki.jqueryui.com/Autocomplete) if appropiate.

Also there doesn't seem to be a solution to this particular problem.