Bug 725842 - Search: fancyqueries dropdown - alignment
Summary: Search: fancyqueries dropdown - alignment
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
low vote
Target Milestone: Unspecified
Assignee: Jason E. Rist
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: katello-blockers
TreeView+ depends on / blocked
 
Reported: 2011-07-26 17:52 UTC by Brad Buckingham
Modified: 2019-09-26 13:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-22 17:50:54 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Brad Buckingham 2011-07-26 17:52:36 UTC
Description of problem:

This bugzilla is follow-up to some IRC chat.

Recommend enhancing the fancyqueries dropdown to have to a dynamic placement in the UI.

Today, if the browser is narrow and the dropdown is selected, there is potential for part of the dropdown to be cut off (e.g. search history or favorites that are very long).  This bugzilla is to request making the vertical placement of the dropdown a bit more dynamic.  For example, automatically shift the dropdown to the left, so that it is completely visible.

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

How reproducible:
always

Steps to Reproduce:
1. go to /notices
2. enter a long search string (e.g. '你好你好你好你好你好你好你好你好你好你好你好你好你好你好你好你好你好你好你好你好你好你好你好你好')
3. click the search dropdown
  
Actual results:
part of the dropdown is cutoff

Expected results:
all contents in dropdown are visible 

Additional info:

Comment 1 Jason E. Rist 2011-09-07 17:52:03 UTC
Fixed in 976701b1640a6929a76f0ba0f1194288a8cff9ac

Comment 2 Corey Welton 2012-01-23 16:49:23 UTC
This seems to be fixed and/or not an issue anymore. Search has been changed a bunch of times, I don't see this behavior exhibited.

QA Verified.

Comment 5 Mike McCune 2013-08-16 17:53:33 UTC
getting rid of 6.0.0 version since that doesn't exist


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