Red Hat Bugzilla – Bug 842838
Content Search: Compare - No way to remove packages/repos from compare, after adding them.
Last modified: 2014-09-18 12:41:43 EDT
Description of problem:
In the content search UI, it is possible to add any number of repos and/or packages for comparison and submit. However, it does not seem possible to actually remove any of these for future comparisons without actually navigating away/reloading the tab.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Sync a variety of different repos -- at least three.
2. Navigate to Content Search and select a Content type of Packages
3. 'Add' multiple repos 3+) and/or packages to your compare using the respective fields in the left-hand pane
4. Submit comparison request
5. Go back to the pane and try to find some way to remove a repo from the compare.
Doesn't appear to be a way to remove a a package or repo. Painful user experience.
Some quick "X" on hover, or something, that allows user to remove a package or repo from comparison consideration.
Katello Version: 0.2.49-1.git.2.b978990.el6_3
fixed in master
I'm not sure I see anything here that fixes the behavior/lack of functionality that I referenced above. I will submit a screenshot. But from within the left panel, I don't see any way to remove repos from consideration after they have been selected.
Created attachment 614054 [details]
As you can see in this screenshot, there doesn't seem to be a way to remove this selected repos. No "x" or anything that allows you to deselect them.
CloudForms System Engine Version: 1.1.12-7.el6cf
This dumb icon keeps dissappearing due to css changes, will take a look.
master commit: e6f2e94d0471d50fc1dfb48da424c1ed7c09fa71
CloudForms System Engine Version: 1.1.12-9.el6cf
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.