JDK-6785497 : PIT : List is not rendered correctly if JScrollPane scrollbar is moved
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6u12
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2008-12-16
  • Updated: 2011-01-19
  • Resolved: 2008-12-16
Related Reports
Duplicate :  
JDK-6779670 - Recursive procedures in the HW/LW Mixing code must traverse parent containers
Relates :  
JDK-6778882 - InternalFrame within glass pane goes below a heavy weight component
Description
I have added few AWT & Swing Components into the JScrollPane. When the frame is realized , o try to navigate the JScrollPane by clicking on the horizontal scrollbar arrow button.  I see that AWT List is not fully rendered. This was working fine in 6u12 b02 promoted build. But now in 6u12 b03 pit build its AWT List is not fully rendered. Hence its a regression introduced in this pit build.   
Workaround for this issue is . I need to minimize the frame & restore to see the AWT List. Even same for the AWT Checkbox which is next to AWTList.  

I have attached the screen shot of the same.  

Step to reproduced:-
-------------------
1) Run the attached testcase.
2) Click on the horizontal scrollbar of the JScrollPane. Observe that AWTList is not fully rendered . If you see the same then the bug is not reproduced.
Comments
WORK AROUND call to validate on the top-level is a possible workaround for the issue, the following code works fine for me Toolkit.getDefaultToolkit().addAWTEventListener( new AWTEventListener() { @Override public void eventDispatched(AWTEvent event) { if (event.getID() == MouseEvent.MOUSE_DRAGGED) { frame.validate(); } } }, AWTEvent.MOUSE_MOTION_EVENT_MASK );
16-12-2008
EVALUATION The bug is a regression of the fix for 6777320 (the fix corrects the equals method of the Region class). The cause of this bug is that HW/LW mixing code doesn't traverse the HW descendants of a container upon a reshaping of the container. The fix for 6779670 will introduce the traversal implementation (please refer to the "suggested fix" section for 6779670 - introducing new method Container.mixOnReshaping should fix the bug).
16-12-2008