Description of problem: The fix for Bug 1926164 breaks accessibility. Keyboard navigation must work for all links, and probably some other things. Version-Release number of selected component (if applicable): 5.0.4-rh84 How reproducible: Easy Steps to Reproduce: 1. Tab to a link or give it focus some other way 2. press enter Actual results: No navigation. Expected results: Navigation is triggered. Additional info:
The enter key has 3 expected behaviors in a form, performing in the standard way is necessary for accessibility. 1. The enter key in a text box should add a new line 2. The enter key in a select box selects the current item 3. The enter key in any other part of the form submits the form The tab key is expected to navigate between elements. To address accessibility issues we will: 1. Revert the enter key to preform the expected actions. 2. Prevent the tab key from selecting items in select boxes.
On QA server. 1: Go to bug edit page. 2: Use tab key to move around page. Tab key always moves focus to the next element. 3: Use enter key in a select box. Current item is selected, form is not submitted. 4: Use enter key in a text area. New lines are added, form is not submitted. 5: Use enter key when a link in the footer has focus. Link is followed. 6: Click enter on other fields. Form is submitted.
This fix has been deployed to stage Bugzilla for a short public testing phase. https://bugzilla.stage.redhat.com
This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.