different behaviour of autocomplete widget on Windows 7 and Unbuntu
Hallo,
I installed the autocomplete widget into a website. One important requirement to the website is that the user can use it only with the keyboard, without a mouse. In order to select an item of the widget's item list I navigate to the item by using the arrow keys and then pressing TAB (not ENTER). The TAB-press causes different behaviour depending on the used operating system.
1) Ubuntu 13.04 (running on a virtual-box-machine), Firefox 20: The selected item is displayed in the text field of the autocomplete widget and the next element on the site is focused. This is the behaviour that I want and expect.
2) Windows 7, Firefox 20: The selected item is displayed in the text field of the autocomplete widget and the AFTER NEXT element is focused. This is the behaviour that I don't want.
Does anybody know how I can prevent case 2)? Are there any blog entries or tutorials referring to this problem? I would also be interested in the code sections of jquery.js and jquery-ui.js that implements the behaviour described above.
I use jquery-1.4.2 and jquery-ui-1.8.9. I also tried jquery-1.9.1 and jquery-ui-1.10.3 but this resulted in additional errors. So I decided to use the older versions.
Thanks
Simon
I installed the autocomplete widget into a website. One important requirement to the website is that the user can use it only with the keyboard, without a mouse. In order to select an item of the widget's item list I navigate to the item by using the arrow keys and then pressing TAB (not ENTER). The TAB-press causes different behaviour depending on the used operating system.
1) Ubuntu 13.04 (running on a virtual-box-machine), Firefox 20: The selected item is displayed in the text field of the autocomplete widget and the next element on the site is focused. This is the behaviour that I want and expect.
2) Windows 7, Firefox 20: The selected item is displayed in the text field of the autocomplete widget and the AFTER NEXT element is focused. This is the behaviour that I don't want.
Does anybody know how I can prevent case 2)? Are there any blog entries or tutorials referring to this problem? I would also be interested in the code sections of jquery.js and jquery-ui.js that implements the behaviour described above.
I use jquery-1.4.2 and jquery-ui-1.8.9. I also tried jquery-1.9.1 and jquery-ui-1.10.3 but this resulted in additional errors. So I decided to use the older versions.
Thanks
Simon
Topic Participants
ralf06021979
scott.gonzalez
mlaird