Bug 1058816 - Regression: CSS broken after redesign: SCAP scan toolbar / Configuration toolbar
Summary: Regression: CSS broken after redesign: SCAP scan toolbar / Configuration toolbar
Keywords:
Status: CLOSED EOL
Alias: None
Product: Spacewalk
Classification: Community
Component: WebUI
Version: 2.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-28 14:56 UTC by Šimon Lukašík
Modified: 2019-10-21 11:50 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-21 11:50:50 UTC
Embargoed:


Attachments (Terms of Use)

Description Šimon Lukašík 2014-01-28 14:56:45 UTC
Description of problem:
With a new web interface of Spacewalk we have the custom toolbar 
misplaced. Previously we had a custom toolbar place in the the upper
right area. Now it is aligned to left. It looks really ugly.

This affects 

    * rhn/systems/details/audit/XccdfDetails.do page
    * configuration management pages (under the rhn/systems folder)

See an example of old custom toolbar (See the text 'diff to previous',
'delete scan', and 'reschedule') at

http://isimluk.fedorapeople.org/sw_openscap/blog/pics/blog-13-detailed-results.jpg

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

How reproducible:
deterministic

Steps to Reproduce:
1. scan system with scap
2. see the details of scan
3.

Actual results:
A toolbar is uglyzed to left

Expected results:
A toolbar is put right

Comment 1 Michael Mráka 2019-10-21 11:50:50 UTC
Spacewalk 2.8 (and older) has already reached it's End Of Life.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before end of life. If you would still like
to see this bug fixed and are able to reproduce it against current version
of Spacewalk 2.9, you are encouraged change the 'version' and re-open it.


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