Search and Top Navigation
#5991 closed bug (fixed)
Opened August 25, 2010 03:13PM UTC
Closed August 31, 2010 12:22PM UTC
Last modified October 11, 2012 09:15PM UTC
Home and End keys trigger search
Reported by: | crussell52 | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | ui.autocomplete | Version: | 1.8.4 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
This behavior can be seen on the remote data demo for autocomplete.
Reproduction:
1. Type "sp" to get suggestions.
2. Select item from list
3. Input is populated with selection, cursor is at end of line.
4. Press Home key
Result: A new search is executed.
Expected: Moving the cursor within the input should not trigger a new search.
A look at the keydown binding adding during _create() shows that the HOME and END key codes are not in the switch statement. These keydowns fall into the "default" case which triggers a search.
Attachments (0)
Change History (6)
Changed August 27, 2010 07:48PM UTC by comment:1
resolution: | → worksforme |
---|---|
status: | new → closed |
Changed August 31, 2010 07:48AM UTC by comment:2
resolution: | worksforme |
---|---|
status: | closed → reopened |
actually it is NOT working.
this is how you can test it is not working:
1) http://jqueryui.com/demos/autocomplete/
2) Type: act
3) Select: ActionScript
4) press: Home button
and you see it does a new search, opening the div under the input text
Changed August 31, 2010 08:56AM UTC by comment:3
resolution: | → fixed |
---|---|
status: | reopened → closed |
Not fixed in 1.8.2, but fixed on GitHub and will be in 1.8.5, see http://view.jqueryui.com/master/demos/autocomplete/default.html
Changed August 31, 2010 12:14PM UTC by comment:4
resolution: | fixed |
---|---|
status: | closed → reopened |
Misunderstood the problem.
Changed August 31, 2010 12:22PM UTC by comment:5
resolution: | → fixed |
---|---|
status: | reopened → closed |
Fixed in dea2f8a7f.
Changed October 11, 2012 09:15PM UTC by comment:6
milestone: | TBD |
---|
Milestone TBD deleted
This was fixed back in 1.8.2.