This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 248083

Summary: Node expansion arrows in "Projects" tab drawn on top of components underneath
Product: platform Reporter: ebakke
Component: JDK ProblemsAssignee: Antonin Nebuzelsky <anebuzelsky>
Status: RESOLVED WONTFIX    
Severity: normal    
Priority: P3    
Version: 8.0.1   
Hardware: PC   
OS: Mac OS X   
Issue Type: DEFECT Exception Reporter:
Attachments: Screenshot illustrating the bug; note the Projects tree view drawing the last expansion arrow over the "Usages" tab
Reproduced in a plain Swing app

Description ebakke 2014-10-21 22:17:09 UTC
Created attachment 150034 [details]
Screenshot illustrating the bug; note the Projects tree view drawing the last expansion arrow over the "Usages" tab

There's some sort of clipping bug that causes the node expansion arrows in the "Projects" tab to be drawn on top of components underneath. See the attached screenshot. The bug can be reproduced by changing the vertical size of the "Projects" pane so that a node expansion arrow appears below the scroll viewport.


Product Version: NetBeans IDE 8.0.1 (Build 201408251540)
Updates: NetBeans IDE is updated to version NetBeans 8.0.1 Patch 1.1
Java: 1.8.0_25; Java HotSpot(TM) 64-Bit Server VM 25.25-b02
Runtime: Java(TM) SE Runtime Environment 1.8.0_25-b17
System: Mac OS X version 10.9.5 running on x86_64; UTF-8; en_US (nb)
User directory: /Users/ebakke/Library/Application Support/NetBeans/8.0
Cache directory: /Users/ebakke/Library/Caches/NetBeans/8.0
Comment 1 Stanislav Aubrecht 2014-10-24 13:22:30 UTC
Created attachment 150103 [details]
Reproduced in a plain Swing app
Comment 2 Stanislav Aubrecht 2014-10-24 13:23:25 UTC
Looks like regression in JDK8u25, the problem is reproducible with plain JTree in a JSplitPane, see attached screen shot.
Comment 3 ebakke 2014-11-03 17:11:08 UTC
Ah, I should probably report against JDK, then. Sorry for the trouble!
Comment 4 ebakke 2016-09-27 12:51:21 UTC
This was a Swing bug that was fixed upstream many months ago; closing.