Indicate the necessity for this enhancement. What does it accomplish?
Fix the tab order of date input fields for predictable tabbing of forms.

Detailed Description

Give a detailed description for the enhancement. Clearly describe all concerns, eliminating ambiguities.
The dateInput.tag does not implement the tabindexOverride attribute that is present in the htmlControlAttribute.tag in Rice 1.0.3, so that can't be used for a fix. It looks like the tabIndex is not defined in the dateInput, so it has a value of 0 and is tab-navigated to after all the attributes that have non-zero values (anything that is a htmlControlAttribute).

Usage Scenarios

Include at least one usage scenario, from the user's task perspective, that might be helpful in understanding the issue:
In KFS (http://testdrive.kfs.kuali.org/kfs-ptd/portal.do) on the Customer Invoice document in the Reccurence Details section below for example:

TAB from "Total Number of Recurrences" should be to "Recurrence Begin Date" (not Active Indicator)

Mocks and Diagrams

Include any mocks (for UI enhancements) or diagrams that might be helpful in understanding the issue:


If applicable, list expectations for performance (optimal and worst cases would be fine, give time in seconds):


Include links to other confluence pages or external resources that might be helpful for this issue:

Requirements Listing

List all requirements (individual verifiable statements) that indicate whether the work for this item has been complete. If there are requirements that are not essential to the functionality but would be nice to have if time allows, enter those under 'Non-Essential':

  1. update the dateInput tag with the necessary tabIndex value to allow for predictable form generation/tabbing
  1. item
  2. item


List any functional or technical work that must be completed before work on this item can begin:

  1. item


List any issues that need to be resolved before work on this item can begin:

  1. the fix mentioned in the related KFS jira was not related to this issue
  1. N/A

QA or Regression Testing Plan

List steps needed to test the basic functionality of this update, enhancement, bug fix

  1. test/steps
  2. test/steps


Functional Analysis Complete? YES (completed by SME)

Needs Review by KAI? No (completed by SME)

Technical Analysis Complete? No (completed by DM)

Needs Review by KTI? No (completed by DM)

Estimate: 30 hours (completed by DM)

Technical Design: Link Here (completed by DM)

Jira: https://jira.kuali.org/browse/KULRICE-6455 (completed by SME)

Final Documentation: Link Here (completed by DM)

Added to QA: No (completed by SME)