Bug 1403190 - Timeline's minus button is corrupted in IE11
Summary: Timeline's minus button is corrupted in IE11
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: GA
: 5.8.0
Assignee: dgutride
QA Contact: Ievgen Zapolskyi
Whiteboard: ui:timeline:trivial
Depends On:
Blocks: 1423033
TreeView+ depends on / blocked
Reported: 2016-12-09 11:41 UTC by Ievgen Zapolskyi
Modified: 2017-06-12 16:52 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1423033 (view as bug list)
Last Closed: 2017-06-12 16:52:46 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:

Attachments (Terms of Use)
screenshot (4.88 KB, image/png)
2016-12-09 11:41 UTC, Ievgen Zapolskyi
no flags Details

Description Ievgen Zapolskyi 2016-12-09 11:41:19 UTC
Created attachment 1229937 [details]

Description of problem:
see screenshot

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Make sure you have any management events for some vm
2. Open Timelines for that vm in IE11
3. Setup Timelines filter and click Apply

Actual results:
minus button is corrupted

Expected results:
it should be displayed correctly

Comment 2 Harpreet Kataria 2016-12-09 17:15:43 UTC

This is also IE related issue, i think you are already aware of this issue, we had discussed this earlier as well.
Let me know if you have questions.


Comment 3 dgutride 2017-01-12 14:53:33 UTC
Moving to POST - a previous fix in timeline view should have addressed this.

Comment 5 dgutride 2017-02-07 18:26:53 UTC
Moving back to Satoe - we need detailed information on what exactly needs info.

Comment 6 Satoe Imaishi 2017-02-07 18:38:13 UTC
As per my comment above, please add a GitHub PR link in the comment so other people can tell which PR fixed the issue.

Comment 7 dgutride 2017-02-15 14:18:25 UTC
This PR was made against the patternfly-timeline and was picked up due to a build in MiQ.  


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