Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 349161 - [ScrolledComposite] Thumb is not shown under certain circumstances
Summary: [ScrolledComposite] Thumb is not shown under certain circumstances
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.5 M1   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-12 20:45 EDT by Rüdiger Herrmann CLA
Modified: 2011-07-19 11:19 EDT (History)
0 users

See Also:

Attachments
Screenshot (132.87 KB, image/png)
2011-06-12 20:46 EDT, Rüdiger Herrmann CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rüdiger Herrmann CLA 2011-06-12 20:45:49 EDT 
If the ScrolledComposite in the DetailedProgressViewer shows a vertical scroll-bar, this scroll-bar does not display a thumb.
Comment 1 Rüdiger Herrmann CLA 2011-06-12 20:46:09 EDT 
Created attachment 197868 [details]
Screenshot
Comment 2 Ivan Furnadjiev CLA 2011-07-19 05:43:29 EDT 
I can reproduce it too. Tested in Firefox, Chrome, Safari and IE.
Comment 3 Ivan Furnadjiev CLA 2011-07-19 09:24:13 EDT 
The reason for this issue is the following: DetailedProgressViewer creates two composites ( "control" and "noEntryArea" ) with the same parent - the ScrolledComposite. They are switched as ScrolledComposite content (ScrolledComposite#setContent is called) in DetailedProgressViewer#updateForShowingProgress. Currently on the client-side, the content of the ScrolledComposite is set in WidgetManager#setParent when a control with ScrolledComposite as parent is created, but not when it is set by ScrolledComposite#setContent on the server. Thus on the client-side, the last created control with ScrolledComposite as parent is set as content without respecting the current state of server-side "content" field. The solution will be to remove parent#setContent from the WidgetManager and synchronize the "content" field trough ScrolledCompositeLCA.
Comment 4 Ivan Furnadjiev CLA 2011-07-19 11:19:10 EDT 
Fixed in CVS HEAD as suggested in comment #3 - remove parent#setContent from the WidgetManager and synchronize the "content" field trough ScrolledCompositeLCA.