Bug 784267 - Subtab decoration doesn't change
Summary: Subtab decoration doesn't change
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Einav Cohen
QA Contact:
URL:
Whiteboard: ux
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-24 12:10 UTC by Jakub Libosvar
Modified: 2016-01-28 21:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-20 07:33:48 UTC
oVirt Team: ---


Attachments (Terms of Use)
Screenshot (32.23 KB, image/png)
2012-01-24 12:10 UTC, Jakub Libosvar
no flags Details

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.


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