Bug 1571064

Summary: Cancel icon displays twice overlaps in the Other Options input box with IE11 browser.
Product: Red Hat Enterprise Linux 7 Reporter: Wei Wang <weiwang>
Component: cockpitAssignee: Martin Pitt <mpitt>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.5CC: bugs, cshao, huzhao, qiyuan, yaniwang, ycui
Target Milestone: pre-dev-freeze   
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: 2021-02-15 07:38:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
picture none

Description Wei Wang 2018-04-24 03:44:21 UTC
Created attachment 1425780 [details]
picture

Description of problem:
Cancel icon displays twice overlaps in the Other Options input box with the IE11 browser.
The issue can only be detected with IE browser.

Version-Release number of selected component (if applicable):
redhat-virtualization-host-4.2.2.1-0.20180420.0
cockpit-160-3.el7.x86_64
cockpit-bridge-160-3.el7.x86_64
cockpit-ws-160-3.el7.x86_64
cockpit-storaged-160-3.el7.noarch
cockpit-ovirt-dashboard-0.11.22-1.el7ev.noarch
cockpit-dashboard-160-3.el7.x86_64
cockpit-system-160-3.el7.noarch


How reproducible:
100%

Steps to Reproduce:
1. Clean install redhat-virtualization-host-4.2.2.1-0.20180420.0 with ks
2. Fill in the Other Options input-box on cockpit login screen
3. Check the cancel icon to the right of the input box


Actual results:
Cancel icon displays twice overlaps with the IE11 browser.


Expected results:
Cancel icon should be displayed correctly in the Other Options input box with the IE11 browser.


Additional info:
The issue cannot be detected with Firefox and Chrome browsers.

Comment 4 RHEL Program Management 2021-02-15 07:38:37 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.