Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.0
-
Fix Version/s: EE-3.0.0.BETA, 3.0.1
-
Component/s: ACE-Components
-
Labels:None
-
Environment:-
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial, Compatibility/Configuration
Description
Currenty, it seems that the user has to click on the arrows in the column headers for sorting an ace:dataTable. However, our UI design guy and the users reported this to be unintuitive because it behaves different than the majority of tables out there in the internet.
Could you please add a mode where it is possible to toggle sorting state by clicking anywhere on the header? Even though it is less efficient to force the user to potentially sort multiple times to get the order they are looking for, it is desirable for some UI scenarios.
Could you please add a mode where it is possible to toggle sorting state by clicking anywhere on the header? Even though it is less efficient to force the user to potentially sort multiple times to get the order they are looking for, it is desirable for some UI scenarios.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Revision #27908
Committed by nils.lundquist
ICE-7676 - Table Sort Revisions: Clickable headers now the default sort mode. Hide alternate sort direction when sorting is active for a column. Allow clicks to individual directions prior to sorting on that column. Give hover state and active state to clickable headers. Disable this behaviour change with clickableHeaderSorting="false" on the table.
Show
Nils Lundquist
added a comment - Revision #27908
Committed by nils.lundquist
ICE-7676 - Table Sort Revisions: Clickable headers now the default sort mode. Hide alternate sort direction when sorting is active for a column. Allow clicks to individual directions prior to sorting on that column. Give hover state and active state to clickable headers. Disable this behaviour change with clickableHeaderSorting="false" on the table.
Note that this feature has already been scheduled for a later release and is not so much a bug as a feature request, so short-term prioritization may require a services effort.