Bug 819931 - Search bar margin is too big when tree context is not system
Summary: Search bar margin is too big when tree context is not system
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Daniel Erez
QA Contact: Tomas Dosek
URL:
Whiteboard: ux
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-08 16:17 UTC by Gilad Chaplik
Modified: 2015-06-19 05:20 UTC (History)
8 users (show)

Fixed In Version: si12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 20:07:58 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gilad Chaplik 2012-05-08 16:17:30 UTC
Search bar is disabled when tree context is not system:

When selecting a tree item (e.g. a data center), one (e.g. "DataCenter: name = XXX") part should be disabled and the other should be free for editing.

Comment 1 Gilad Chaplik 2012-05-10 09:13:35 UTC
Another related issue, we also need to disable navigating to the hidden tab (in the browser url bar), e.g. in case volume tab is hidden we can't navigate to 
"http://XXX/webadmin/volumes.

Comment 2 Gilad Chaplik 2012-05-21 09:32:02 UTC
At first I thought the search bar is disabled, but Einav discovered that the search bar is enabled and the margin for the its text-box is very big, and it's located at an un-intuitive place.

changing the bug header.

Comment 3 Vojtech Szocs 2012-05-21 13:45:36 UTC
> Another related issue, we also need to disable navigating to the hidden tab (in the browser url bar), e.g. in case volume tab is hidden we can't navigate to 
"http://XXX/webadmin/volumes.

Covered by patch [http://gerrit.ovirt.org/4622].

Comment 5 Daniel Erez 2012-07-29 18:57:30 UTC
git commit 85b4fe49b8d4c125368fae6ab434a35aa1408fb9

Comment 6 Tomas Dosek 2012-07-31 08:23:05 UTC
Verified - si12 - above described scenario no longer reproduces. Seach bar is correctly displayed and serach works fine accordingly to description in comment #1.


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