Hi, Phil. I have only two questions: - Does it mean that we do not support "ontop" property via public API in idk? - Probably the name should contain «owner» instead of «parent»?, But since this is not a public API I guess it is not an issue.
> > > This has an FX bug + webrev : > https://bugs.openjdk.java.net/browse/JDK-8088395 > <https://bugs.openjdk.java.net/browse/JDK-8088395> > http://cr.openjdk.java.net/~prr/8088395/index.html > <http://cr.openjdk.java.net/%7Eprr/8088395/index.html> > > and also a JDK-side fix and webrev :- > https://bugs.openjdk.java.net/browse/JDK-8176530 > <https://bugs.openjdk.java.net/browse/JDK-8176530> > http://cr.openjdk.java.net/~prr/8176350/ > <http://cr.openjdk.java.net/~prr/8176350/> > > The problem is FX modal dialogs are ignoring the Window parameter. > We can fix the problem with disabling the modal parent on the FX side > and that is why most files in FX are updated. > > But it does not fix the "on top" issue which requires the JDK fixes and > to pass in the DialogOnTop private attribute. > The JDK code is there solely for FX and won't have any visibility > unless FX passes in the private attribute. > > On Linux it uses the standard AWT "always on top" modality > On windows it uses the HWND for the FX window and windows native modality > On Mac you won't see anything since Mac does this automatically > > -phil.
