Details
-
Type:
Task
-
Status: Closed
-
Priority:
Major
-
Resolution: Complete
-
Affects Version/s: 2.2
-
Fix Version/s: 2.5
-
Component/s: Development, Roadmap, User Experience (UX)
-
Security Level: Public (Public: Anyone can view)
-
Labels:None
-
Epic Link:
-
Rice Module:KRAD
-
KRAD Feature Area:UIF Component
-
Application Requirement:KS
-
Sprint:2.5.0-m1 Sprint 1, 2.5.0-m1 Sprint 2
-
KAI Review Status:Not Required
-
KTI Review Status:Not Required
Description
"KRAD should include standard encoded semantics that support keyboard access to all its functionality. People who can't use a mouse should be able to use a keyboard to do all the tasks that are presented through the KRAD UI framework.
Additonally, Applications should be able to define custom keyboard shortcuts for their unique functions that are not covered by KRAD's support for the standard keyboard shortcuts."
More info... https://wiki.kuali.org/display/KULRICE/KRAD+-+Keyboard+support
For enter key support, see:
Attachments
Issue Links
- fixes
-
KULRICE-8396 Pressing Enter with cursor in search field gives inappropriate messages on Several KRMS Rules Search Interfaces
-
- Open
-
- is duplicated by
-
KULRICE-10902 Support enter key action
-
- Closed
-
-
KULRICE-11587 Analysis: Support enter key action
-
- Closed
-
- is related to
-
KULRICE-9038 Lookup - execute search when hitting enter while in any of the criteria text fields
-
- Closed
-
- relates to
-
KSENROLL-6910 Investigate make a button the default action on a page
-
- Open
-
-
KRRM-141 KRAD Phase 3 - Complete core features needed by KS
-
- Resolved
-
KFS has a need to configure the enter key per document (use case: power users in accounts payable)