Bug 1323972 - WebUI - alert-error class instead of alert-danger for styling the error notifications on Users page
Summary: WebUI - alert-error class instead of alert-danger for styling the error notif...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Roman Plevka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-05 08:41 UTC by Roman Plevka
Modified: 2019-09-26 16:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-27 20:44:15 UTC
Target Upstream Version:


Attachments (Terms of Use)
screenshot of the alert css styling error (127.34 KB, image/png)
2016-04-05 09:20 UTC, Roman Plevka
no flags Details

Description Roman Plevka 2016-04-05 08:41:19 UTC
Description of problem:
the jnotify-container element displays error messages with obsolete "alert-error"
class name instead of "alert-danger". This results in transparent notification balloon. (see attached screenshot)


Version-Release number of selected component (if applicable):
6.2.0 snap6.1

How reproducible:
always

Steps to Reproduce:
1. make sure foreman does not have a valid email settings
2. navigate to administer -> users
3. select any user -> email preferences tab
4. click "test email"

Actual results:
transparent error balloon pops out (with non existing "alert-error" class assigned)

Expected results:
the popup uses "alert-danger" class so it is styled properly

Additional info:

Comment 2 Roman Plevka 2016-04-05 09:20:17 UTC
Created attachment 1143723 [details]
screenshot of the alert css styling error

Comment 3 Bryan Kearney 2017-03-27 20:44:15 UTC
I do not see us adressing this in the next few releases. I am therefore closing this out. If you feel that this is a mistake, please feel free to re-open with additional information.


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