Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Complete
    • Affects Version/s: 2.2
    • Fix Version/s: 2.5
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-6752UI Framework - Keyboard Support
      KULRICE-6753UI Framework - Keyboard Support
      KULRICE-12054Document enter key support
      KULRICE-10902Support enter key action
      KULRICE-11587Analysis: Support enter key action
      KULRICE-11588Analysis: Support enter key action
      KULRICE-11589Analysis: Support enter key action
      KULRICE-11590Analysis: Support enter key action
      KULRICE-5368Uif Framework - Add support for enter key
      KULRICE-6754Document the UI Framework - Keyboard Support
    • 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

        Issue Links

          Activity

          Hide
          Matt Sargent added a comment -

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

          Show
          Matt Sargent added a comment - KFS has a need to configure the enter key per document (use case: power users in accounts payable)
          Show
          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
          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
          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
          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
          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
          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
          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
          Jerry Neal (Inactive) added a comment -

          This issue needs split into sub-tasks

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

            People

            • Assignee:
              Tadas Paegle (Inactive)
              Reporter:
              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

                  Agile

                    Structure Helper Panel