Bug 784355 - Relevant Errata - Closing underlying system view can cause zombie errata info view
Summary: Relevant Errata - Closing underlying system view can cause zombie errata info...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-24 16:51 UTC by Corey Welton
Modified: 2018-08-30 21:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-18 17:38:05 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Corey Welton 2012-01-24 16:51:18 UTC
Description of problem:
When closing a system view while viewing errata details can cause that window to get stuck, obstructing view

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


How reproducible:


Steps to Reproduce:
1.  Synch RH content and register a system to katello.  Associate system with RH repo.
2.  Navigate to systems and click on the system you registered.
3.  Click on the errata subtab in the system view; click the (I) info icon for any given errata
4.  While errata info is opened, click the underlying "Close" link; view results
  
Actual results:
System view is closed but errata info window remains.  Note that the typical behavior of this window (remove soft focus results in closure) does not take place in this scenario.

Expected results:
* Errata window should close and/or User should not be able to close system view while this is open
* should we have a close link/button on the errata windows, just to assure they can always be closed?

Additional info:

Comment 2 Mike McCune 2014-03-18 17:38:05 UTC
This bug was closed because of a lack of activity.  If you feel this bug should be reconsidered for attention please feel free to re-open the bug with a comment stating why it should be reconsidered.


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