Bug 1312750 - when in responsive mode, filter input-box hides expanded menu
Summary: when in responsive mode, filter input-box hides expanded menu
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-29 08:04 UTC by Jan Hutař
Modified: 2017-02-08 22:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-08 22:01:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
expanded menu in responsive mode is hidden by filter input box (17.00 KB, image/png)
2016-02-29 08:05 UTC, Jan Hutař
no flags Details

Description Jan Hutař 2016-02-29 08:04:29 UTC
Description of problem:
When you are in Firefox's responsive mode (360x640), filter input-box hides expanded menu


Version-Release number of selected component (if applicable):
Satellite-6.2.0-RHEL-7-20160228.1


How reproducible:
always


Steps to Reproduce:
1. In Firefox use menu -> Developer -> Responsive Design View
2. Set screen size to 360x640
3. Go to ".../hosts" and expand Satellite6 menu 


Actual results:
Filter input-box is rendered above expanded menu


Expected results:
Filter input-box should not hide expanded menu

Comment 1 Jan Hutař 2016-02-29 08:05:54 UTC
Created attachment 1131441 [details]
expanded menu in responsive mode is hidden by filter input box

Comment 3 Bryan Kearney 2016-07-26 15:25:24 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 4 Bryan Kearney 2016-07-26 15:34:49 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 6 Bryan Kearney 2017-02-08 22:01:26 UTC
I do not envision this bug being addressed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.


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