Ticket #2528552 (closed defect)
Reporter Steven Hartland |
Opened: 10/8/09 Last modified: 04/13/11 Status: closed Type: defect Resolution: fixed |
Owner  Jenny Donnelly |
Target Release: 2.9.0 Priority: P3 (normal) |
|---|---|---|---|
| Summary: | autocomplete doesnt recognise arrowed selections when force selection is set | ||
| Description: | When a user types in a partial then uses arrows to highlight an option that is subsequently set in the text box with force selection in effect the selectionEnforceEvent is fired as though the users This is incorrect as although the result is the user has selected one of the available options. |
||
| Type: | defect | Observed in Version: | 2.7.0 |
| Component: | AutoComplete | Severity: | S3 (normal) |
| Assigned To: | Jenny Donnelly | Target Release: | 2.9.0 |
| Location: | Priority: | P3 (normal) | |
| Tags: | Relates To: | ||
| Browsers: | N/A | ||
| URL: | |||
| Test Information: | With an autocomplete set with forceSelection: true |
||
Change History
|
Posted: 11/6/09
|
|
Posted: 11/7/09
|
|
Posted: 12/20/10
|
|
Posted: 04/13/11
|
created 8da8d32: "[fix bug #2528552] typeAhead with forceSelection should not clear input if user arrows-to-selection then blurs the widget, when input value has been updated via typeAhead."
Small clarification here: if typeAhead is *not* enabled, then input may be cleared. This is because clicking away indicates the end of an interaction, and the input will be cleared if what has been typed does not match one of the suggestions. This is the nature of the enforceSelection feature.