Bug 1571064 - Cancel icon displays twice overlaps in the Other Options input box with IE11 browser.
Summary: Cancel icon displays twice overlaps in the Other Options input box with IE11 ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cockpit
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: pre-dev-freeze
: ---
Assignee: Martin Pitt
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-24 03:44 UTC by Wei Wang
Modified: 2021-02-15 07:38 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-15 07:38:37 UTC
Target Upstream Version:


Attachments (Terms of Use)
picture (47.28 KB, image/png)
2018-04-24 03:44 UTC, Wei Wang
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.