Bug 1394249

Summary: UX: notification bell should be centered between two lines
Product: Red Hat CloudForms Management Engine Reporter: Matouš Mojžíš <mmojzis>
Component: UI - OPSAssignee: Eric Winchell <ewinchel>
Status: CLOSED ERRATA QA Contact: Matouš Mojžíš <mmojzis>
Severity: low Docs Contact:
Priority: medium    
Version: 5.7.0CC: dajohnso, hkataria, jhardy, mmojzis, mpovolny, obarenbo
Target Milestone: GA   
Target Release: 5.8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: notification
Fixed In Version: 5.8.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-31 14:23:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Attachments:
Description Flags
bell not centered none

Description Matouš Mojžíš 2016-11-11 13:26:13 UTC
Description of problem:


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

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
Notification bell is aligned to the right.

Expected results:
It should be centered.

Additional info:

Comment 4 Matouš Mojžíš 2016-11-14 16:28:32 UTC
Created attachment 1220479 [details]
bell not centered

Comment 6 CFME Bot 2016-11-14 20:32:16 UTC
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/630760c194deedc2e8fd6bc6ca4d029872f01246

commit 630760c194deedc2e8fd6bc6ca4d029872f01246
Author:     Eric Winchell <ewinchel>
AuthorDate: Mon Nov 14 14:43:35 2016 -0500
Commit:     Eric Winchell <ewinchel>
CommitDate: Mon Nov 14 14:43:35 2016 -0500

    Correct notification bell styling
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1394249

 app/views/layouts/_header.html.haml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comment 7 Matouš Mojžíš 2017-03-06 10:50:07 UTC
Verified in 5.8.0.3. Lines were removed.

Comment 9 errata-xmlrpc 2017-05-31 14:23:19 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHSA-2017:1367