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 242809

Summary: Floating window on secondary monitory pops back to primary monitor (MacOS)
Product: platform Reporter: ebakke
Component: Window SystemAssignee: Stanislav Aubrecht <saubrecht>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: P3    
Version: 7.4   
Hardware: PC   
OS: Mac OS X   
Issue Type: DEFECT Exception Reporter:

Description ebakke 2014-03-11 19:37:55 UTC
I'm observing floating window behavior on MacOS Mavericks that makes floating windows unable to be reliably used on secondary monitors.

To reproduce:
1) Configure your Mac in multi-monitor mode. In my case I have an external display as the primary display and a laptop display as a secondary one.
2) Open up NetBeans and maximize it on the primary display.
3) Open the Properties tab (Window->IDE Tools->Properties).
4) Right-click the docked properties tab and click "Float".
5) Drag the floating properties window by the title bar completely over to the secondary display.
6) Click the title bar of the main NetBeans window to make it the active window.
7) Now click the title bar of the floating windows with the Properties tab. The floating window pops back to the primary display. (And if you drag the title bar at this point instead of releasing the mouse button, you will see the window move way over on the primary display while the lonely mouse cursor is moving on the secondary display.)


Product Version: NetBeans IDE 7.4 (Build 201310111528)
Updates: Updates available to version NetBeans 7.4 Patch 2
Java: 1.8.0-ea; Java HotSpot(TM) 64-Bit Server VM 25.0-b59
Runtime: Java(TM) SE Runtime Environment 1.8.0-ea-b117
System: Mac OS X version 10.9.2 running on x86_64; UTF-8; en_US (nb)
User directory: /Users/ebakke/Library/Application Support/NetBeans/7.4
Cache directory: /Users/ebakke/Library/Caches/NetBeans/7.4
Comment 1 Stanislav Aubrecht 2014-03-14 09:39:16 UTC

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