Bug 808588 - (Google Chrome) System Templates: Search bar/icon in Eligible Content missing.
Summary: (Google Chrome) System Templates: Search bar/icon in Eligible Content missing.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: Unspecified
Assignee: Brad Buckingham
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-30 19:13 UTC by Corey Welton
Modified: 2013-08-16 18:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-09 15:25:23 UTC
Target Upstream Version:

Attachments (Terms of Use)
screenshot (22.80 KB, image/png)
2012-03-30 19:17 UTC, Corey Welton 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Corey Welton 2012-03-30 19:13:36 UTC 
Description of problem:

When using google chrome, the magnifying glass icon for Eligible content no longer renders and is non-functional.

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


How reproducible:


Steps to Reproduce:
1.  Create and sync third party repo
2.  Navigate to Content Management > System Templates
3.  Observe the Eligible Content pane
4.  Drill down into $repo > Packages
5.  Observe pane  

Actual results:
Step 3: No icon
Step 5: No icon

Expected results:
Step 3: Should be a grayed-out (nonusable) icon
Step 5: Should be a functional icon/search tool.

Additional info:
Comment 1 Corey Welton 2012-03-30 19:17:20 UTC 
Created attachment 574079 [details]
screenshot

Note:  workaround is that user can of course use the search in the right pane after selecting a template. This is nonetheless a regression.
Comment 2 Mike McCune 2012-05-09 15:25:23 UTC 
Not a browser specific issue, we never had that search icon on the left pane.

Re-design work is being done to address finding and adding content to System Templates which should address the overall issue so I'm going to close this.
Comment 4 Mike McCune 2013-08-16 18:05:21 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.