Bug 281193 - Repaint problem on scrollbar
Summary: Repaint problem on scrollbar
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Felipe Heidrich CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-23 04:45 EDT by utilisateur_768 CLA
Modified: 2019-09-06 16:08 EDT (History)
2 users (show)

See Also:

Attachments
screen shot (1.84 MB, image/png)
2009-06-23 10:20 EDT, Kevin Barnes 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 utilisateur_768 CLA 2009-06-23 04:45:54 EDT 
Build id: I20090528-2000

Today, when switching back from "Chrome" browser, showing some flash, to eclipse, the vertical scrollbar of the package explorer view was not repainted. The whole bar, with the "down" button at the bottom of the bar was not repainted. When trying again, i managed to get some "not-buffered" painting artifact, but no "forget-to-repaint" again.
Comment 1 Felipe Heidrich CLA 2009-06-23 10:04:24 EDT 
Can you reproduce this problem consistently?

can you take a screenshot next time if see the problem ?
Comment 2 utilisateur_768 CLA 2009-06-23 10:11:36 EDT 
No i cannot reproduce the problem consistently. The screenshot would be useless : eclipse was almost completely repainted (execpt the vertical scrollbar of the package explorer), and the "not-repainted" zone was filled with the unmodified web page part (since it's web browser which was drawn before i switched to eclipse).
Comment 3 Kevin Barnes CLA 2009-06-23 10:20:11 EDT 
Created attachment 139876 [details]
screen shot

I've seen this a couple times this week. Haven't found a pattern to it yet.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:08:21 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.