Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-8860

Keyboard Support (enter key, other short cuts)

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Complete
    • Affects Version/s: 2.2
    • Fix Version/s: 2.5
    • 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:

      https://wiki.kuali.org/display/KULRICE/Enter+Key+Support

        Attachments

          Issue Links

            Activity

            Hide
            masargen Matt Sargent added a comment -

            KFS has a need to configure the enter key per document (use case: power users in accounts payable)

            Show
            masargen Matt Sargent added a comment - KFS has a need to configure the enter key per document (use case: power users in accounts payable)
            Show
            jkneal Jerry Neal (Inactive) added a comment - For more details, see https://wiki.kuali.org/display/KULRICE/KRAD+-+Keyboard+support Related JIRAs: KULRICE-5368 KULRICE-5512 KFSMI-742 KFSMI-2761 KFSMI-4545 KSLAB-1339 KSLAB-1341
            Hide
            masargen Matt Sargent added a comment -

            The handling of focus issues when transitioning too and from light boxes should be part of this effort. Should that be recorded as a subtask JIRA?

            Show
            masargen Matt Sargent added a comment - The handling of focus issues when transitioning too and from light boxes should be part of this effort. Should that be recorded as a subtask JIRA?
            Hide
            masargen Matt Sargent added a comment -

            Along with the enter key, the ability for applications to define their own shortcuts needs to be supported. We'll need a list of of these and should create subtasks for those

            Show
            masargen Matt Sargent added a comment - Along with the enter key, the ability for applications to define their own shortcuts needs to be supported. We'll need a list of of these and should create subtasks for those
            Hide
            mis306 Michelle Suranofsky added a comment -

            As discussed during our 2/22/13 OLE UX Meeting, here are some examples of the types of keyboard shortcuts OLE is looking for: insert a repeatable field on a form (above or below current field), move a field on a form up or down one, trigger events like validation or reformat.

            Show
            mis306 Michelle Suranofsky added a comment - As discussed during our 2/22/13 OLE UX Meeting, here are some examples of the types of keyboard shortcuts OLE is looking for: insert a repeatable field on a form (above or below current field), move a field on a form up or down one, trigger events like validation or reformat.
            Hide
            jkneal Jerry Neal (Inactive) added a comment -

            This issue needs split into sub-tasks

            Show
            jkneal Jerry Neal (Inactive) added a comment - This issue needs split into sub-tasks

              People

              • Assignee:
                tpaegle Tadas Paegle (Inactive)
                Reporter:
                wwashington William Washington (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 2 weeks, 3 days
                  2w 3d
                  Remaining:
                  Time Spent - 1 week, 4 days, 6 hours Remaining Estimate - 3 days, 2 hours
                  3d 2h
                  Logged:
                  Time Spent - 1 week, 4 days, 6 hours Remaining Estimate - 3 days, 2 hours
                  1w 4d 6h