Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.8.2-EE-GA_P01, 1.8.3
-
Component/s: ICE-Components
-
Labels:None
-
Environment:All
Description
Any of the select based input components, which use onchange to do a partial submit, such as selectOneListbox, selectManyListbox and selectManyMenu, have an issue with keyboard navigation. On the one hand, a user may need to press the down arrow, in the select, to get to their desired option, somewhere down the list, and won't want to incur the latency of partial submits as they go. On the other hand, an application may wish for users to cycle through their options, updating the rest of the display as they go. So we need to differentiate between selections that are just the user flitting through, versus selections where the user wishes to remain for a bit, and only partial submit in the latter.
We'll use the selectInputText technique of using a timer, so that multiple change events within a certain time range will result in only the last one causing a partial submit.
We'll use the selectInputText technique of using a timer, so that multiple change events within a certain time range will result in only the last one causing a partial submit.
Issue Links
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
| Field | Original Value | New Value |
|---|---|---|
| Salesforce Case | [] | |
| Fix Version/s | 1.8.2-EE-GA_P01 [ 10220 ] | |
| Fix Version/s | 1.8.3 [ 10211 ] | |
| Assignee Priority | P1 | |
| Assignee | Mark Collette [ mark.collette ] |
| Salesforce Case | [] | |
| Description |
Any of the select based input components, which use onchange to do a partial submit, such as selectOneListbox and possibly selectOneMenu, have an issue with keyboard navigation. On the one hand, a user may need to press the down arrow, in the select, to get to their desired option, somewhere down the list, and won't want to incur the latency of partial submits as they go. On the other hand, an application may wish for users to cycle through their options, updating the rest of the display as they go. So we need to differentiate between selections that are just the user flitting through, versus selections where the user wishes to remain for a bit, and only partial submit in the latter. We'll use the selectInputText technique of using a timer, so that multiple change events within a certain time range will result in only the last one causing a partial submit. |
Any of the select based input components, which use onchange to do a partial submit, such as selectOneListbox, selectManyListbox and selectManyMenu, have an issue with keyboard navigation. On the one hand, a user may need to press the down arrow, in the select, to get to their desired option, somewhere down the list, and won't want to incur the latency of partial submits as they go. On the other hand, an application may wish for users to cycle through their options, updating the rest of the display as they go. So we need to differentiate between selections that are just the user flitting through, versus selections where the user wishes to remain for a bit, and only partial submit in the latter. We'll use the selectInputText technique of using a timer, so that multiple change events within a certain time range will result in only the last one causing a partial submit. |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Assignee Priority | P1 | |
| Assignee | Mark Collette [ mark.collette ] |