Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-3.3.0.GA_P01
-
Fix Version/s: EE-3.3.0.GA_P02, 4.0
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Firefox
-
Assignee Priority:P2
-
Support Case References:
Description
In Firefox, after entering text to the autoCompleteEntry input field, using the arrow keys to navigate to an option, each single keypress causes the focus/highlight to move down two options.
This makes selecting a value via the keyboard in FF some what difficult. This issue can be reproduced with the Showcase demo.
This makes selecting a value via the keyboard in FF some what difficult. This issue can be reproduced with the Showcase demo.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Carmen Cristurean [ ccristurean ] | |
| Fix Version/s | EE-3.3.0.GA_P02 [ 11371 ] | |
| Fix Version/s | 4.0 [ 11382 ] | |
| Affects Version/s | EE-3.3.0.GA_P02 [ 11371 ] | |
| Assignee Priority | P2 [ 10011 ] |
| Assignee | Carmen Cristurean [ ccristurean ] | Mircea Toma [ mircea.toma ] |
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #40453 | Thu Mar 27 14:38:00 MDT 2014 | mircea.toma | |
| Files Changed | ||||
MODIFY
/icefaces4/trunk/icefaces/ace/component/resources/icefaces.ace/autocompleteentry/autocompleteentry.js
|
The issue occurs because there are two callbacks registered for key events. This is a regression introduced by the fix for ICE-9327.
Show
Mircea Toma
added a comment - The issue occurs because there are two callbacks registered for key events. This is a regression introduced by the fix for ICE-9327 .
The applied fix unbinds the 'onkeyup' callback in case the 'onkeypress' callback is invoked. In the use case described by ICE-9327 when the 'onkeypress' is not invoked the additional 'onkeyup' will be the one (and only one) invoking the callback.
Show
Mircea Toma
added a comment - - edited The applied fix unbinds the 'onkeyup' callback in case the 'onkeypress' callback is invoked. In the use case described by ICE-9327 when the 'onkeypress' is not invoked the additional 'onkeyup' will be the one (and only one) invoking the callback.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Verified with EE4 trunk/EE-3.3.0-maintenance branch # 40474 using showcase > ace:autoCompleteEntry, in FF27, IE10, Chrome33.
Show
Carmen Cristurean
added a comment - Verified with EE4 trunk/EE-3.3.0-maintenance branch # 40474 using showcase > ace:autoCompleteEntry, in FF27, IE10, Chrome33.
Verified with ACE regressions on ee-3.3.0 maintenance branch, revision #40475.
Show
Liana Munroe
added a comment - Verified with ACE regressions on ee-3.3.0 maintenance branch, revision #40475.
| Status | Resolved [ 5 ] | Closed [ 6 ] |
This issue is reproducible in FF27/17/3.6 with EE-3.3.0.GA_P01 release code, EE-3.3.0.GA-maintenance branch# 40368, and IF4 trunk# 40367 (using showcase > autoCompleteEntry demos, and component QA test app).
This issue was missed by automation, most of the automated tests passing for showcase > autoCompleteEntry. However none of our tests use the arrow keys, because arrow keys movements and submits are unreliable in selenium1. This type of tests will be added to the WebDriver tests for autoCompleteEntry ACE tests.
Manual testing failed to catch this issue, probably because of the way we all performed this testing. In order to see this issue, one must press the keys at a slower pace, and we probably failed to do this.