Bug 1287307 - Inconsistent use of scrollbars in the UI
Summary: Inconsistent use of scrollbars in the UI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: WebUI
Version: 6.1.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Walden Raines
QA Contact: Shimon Shtein
URL: http://projects.theforeman.org/issues...
Whiteboard: Non-nutupane
Depends On:
Blocks: 1317008
TreeView+ depends on / blocked
 
Reported: 2015-12-01 22:50 UTC by Stuart Auchterlonie
Modified: 2019-04-01 20:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:42:01 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Foreman Issue Tracker 16534 None None None 2016-12-19 20:00:50 UTC
Red Hat Knowledge Base (Solution) 2121121 None None None 2016-01-12 16:02:09 UTC

Description Stuart Auchterlonie 2015-12-01 22:50:04 UTC
Description of problem:

The use of scrollbars in the UI is inconsistent leading to a bad
user experience.

In some areas, such as

- Content View > {View Name} > Yum Content > filters > {filter name} > affected repositories, there is only a single scroll bar which allows scrolling from
the top of the pane to the bottom of the pane. This is a *NICE* experience.

In other areas, such as

- Activation keys > {key name} > subscriptions > add, there are multiple scroll 
bars, one for the whole pane, and one for just the subscriptions to add. This
is *NOT* a nice experience

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

6.1.3, 6.1.4

How reproducible:

100%

Steps to Reproduce:
1. Navigate to the sections described aboce
2.
3.

Actual results:

Scroll bars are applied differently in different areas of the UI

Expected results:

Consistent use of scroll bars throughout the UI

Additional info:

Comment 3 Walden Raines 2016-12-19 19:40:04 UTC
Connecting redmine issue http://projects.theforeman.org/issues/16534 from this bug

Comment 4 Bryan Kearney 2016-12-19 21:01:20 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16534 has been resolved.

Comment 6 Bryan Kearney 2018-02-21 16:39:58 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-2018:0336

Comment 7 Bryan Kearney 2018-02-21 16:42:01 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-2018:0336

Comment 8 pm-sat@redhat.com 2018-02-21 16:49:54 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-2018:0336


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