Bug 535856

Summary: Yast "category" selection doesn't expose all elements of category
Product: [openSUSE] openSUSE 11.2 Reporter: John Pemberton <Pemberton.John.M>
Component: YaST2Assignee: E-mail List <bnc-team-screening>
Status: VERIFIED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None    
Version: Milestone 6   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Yast "misc" category click result
Expected result after click on "Misc" category

Description John Pemberton 2009-09-01 07:37:29 UTC
Created attachment 316116 [details]
Yast "misc" category click result

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.2) Gecko/20090730 SUSE/3.5.2-2.4 Firefox/3.5.2

New install selected, from images, choosing KDE, but modified partition
proposal to keep "/home" partition used with M5.

When a "category" from the list on the left of the yast control center is selected, if necessary an attempt is made to scroll the right hand side to the elements of the selected category.  But I'd expect all the elements of the category to be exposed by the scrolling.  Instead, sometimes only some elements are visible even if the window is plenty big enough to view them all.

Reproducible: Always

Steps to Reproduce:
1. Enter yast control center
2. Size window so that on the right hand side you can see about the top half of the first row of the Network Sevices category.
3. On the left hand side, click on "Network Services" or any category below it that had more than one row of elements on the left hand side.  You'll generally only see one or two rows of the elements of the category on the right side, not all.
Comment 1 John Pemberton 2009-09-01 07:42:26 UTC
Created attachment 316117 [details]
Expected result after click on "Misc" category
Comment 2 Katarina Machalkova 2009-09-01 08:18:39 UTC
Known and already fixed issue

*** This bug has been marked as a duplicate of bug 525288 ***