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

Bug 1533389

Summary: [UI] - 'Manage Networks' dialog - Fix minor issue with the radio buttons and headers focus
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: Frontend.WebAdminAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: low Docs Contact:
Priority: low    
Version: 4.2.0CC: bugs, danken, gshereme, tjelinek
Target Milestone: ovirt-4.3.0Flags: rule-engine: ovirt-4.3+
rule-engine: ovirt-4.4+
Target Release: 4.3.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.0_alpha Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-13 07:46:38 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
record1 none

Description Michael Burman 2018-01-11 09:04:34 UTC
Created attachment 1379890 [details]
record1

Description of problem:
[UI] - 'Manage Networks' dialog - Fix minor issue with the radio buttons and headers focus.

There is left a minor issue with the focus in this dialog and this bug will track this issue. 

Version-Release number of selected component (if applicable):
4.2.1-0.2.el7

How reproducible:
100%

Steps to Reproduce:
1. Open the manage network dialog , press on the default route radio button and then press on 'Assign all' or 'Required all' checkbox

Actual results:
The focus forced back to the radio button. 

Expected results:
The focus should remain on the left.

Additional info:
See also - BZ 1494917

Comment 1 Michael Burman 2018-10-16 10:27:16 UTC
Verified on - 4.3.0-0.0.master.20181015155431.git4a9d480.el7

Comment 2 Sandro Bonazzola 2018-11-02 14:29:51 UTC
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.7 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.

Comment 3 Sandro Bonazzola 2018-11-02 14:51:05 UTC
Closed by mistake, moving back to qa -> verified

Comment 4 Sandro Bonazzola 2019-02-13 07:46:38 UTC
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.