Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1425128

Summary: unexpected TAB key order in the new logical network window
Product: [oVirt] ovirt-engine Reporter: Mor <mkalfon>
Component: Frontend.WebAdminAssignee: Marcin Mirecki <mmirecki>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: low Docs Contact:
Priority: low    
Version: 4.1.1CC: bugs, gshereme, mburman
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-29 14:15:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
window with the bug none

Description Mor 2017-02-20 16:00:38 UTC 
Description of problem:
When creating a new logical network with the "Create on external provider" checkbox marked, 
in the Subnets tab, the TAB key is not working as expected.

Version-Release number of selected component (if applicable):
Red Hat Virtualization Manager Version: 4.1.1.2-0.1.el7

How reproducible:
100%

Steps to Reproduce:
1. Add external network provider to engine.
2. Create new network on the external provider.
3. Click on the subnets tab.
4. Mark the "Create Subnet" checkbox.
5. Place the cursor on the first textbox - Name.
6. Press TAB.

Actual results:
Cursor is located at the DNS textbox.

Expected results:
Cursor should be located at the second textbox, CIDR. 
If you press TAB multiple times, the order of the cursor should be located at the Name textbox.

Additional info:
Comment 1 Mor 2017-02-20 16:05:22 UTC 
Created attachment 1255731 [details]
window with the bug
Comment 2 Yaniv Kaul 2017-02-21 09:02:41 UTC 
We don't have correct tab order anywhere. There's a general bug about it somewhere. I don't see the point in opening bugs per specific dialog.
Comment 3 Mor 2017-02-21 09:21:14 UTC 
(In reply to Yaniv Kaul from comment #2)
> We don't have correct tab order anywhere. There's a general bug about it
> somewhere. I don't see the point in opening bugs per specific dialog.

I opened additional bug for this dialog because the previous patch fixed an issue with another dialog. I can close this bug if the general one covers all.
Comment 4 Marcin Mirecki 2017-05-29 14:15:45 UTC 
The order bug is a duplicate of BZ 1425149.

Cycling to the begging after a number of 'tabs' is a different problem.
We do not have this on any of our dialogs. I think this deserves a separate, general bug

*** This bug has been marked as a duplicate of bug 1425149 ***