Bug 784267

Summary: Subtab decoration doesn't change
Product: [Retired] oVirt Reporter: Jakub Libosvar <jlibosva>
Component: ovirt-engine-webadminAssignee: Einav Cohen <ecohen>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, ecohen, iheim, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: ux
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-20 07:33:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Screenshot none

Description Jakub Libosvar 2012-01-24 12:10:17 UTC
Created attachment 557216 [details]
Screenshot

Description of problem:
Decoration for currently chosen subtab in Storage tab doesn't change when changing from Template Import subtab to VM Import subtab while in Template Import subtab is selected some item.

Version-Release number of selected component (if applicable):
ovirt-engine-webadmin-portal-3.0.0_0001-1.3.fc16.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Have an export domain attached with some templates exported on it
2. Go to Storage tab and select export domain
3. Select Template Import subtab
4. Select some template
5. Change subtab to VM Import
  
Actual results:
VM Import subtab is not changed to selected subtab but the content is

Expected results:
VM Import subtab is marked as currently selected subtab (white)

Additional info:
Screenshot attached

Comment 1 Jakub Libosvar 2012-01-24 12:19:09 UTC
Note that when this happens, user can't operate with exported VMs on export domain cause Restore and Remove buttons are inactive even if some VM is selected. After subtabs are changed (e.g. to General and back to VM Import), everything works fine.

Comment 2 Itamar Heim 2012-12-20 07:33:48 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.