Hi Anthony,
this problem is specific only for applets and doesn't touch usual
application,
now I think the best place for this code is PluginEmbeddedFrame.
I'll check this...
Thanks,
Mikhail.
On 4/9/2014 3:08 PM, Anthony Petrov wrote:
Hi Michail,
Instead of handling the WINDOW_CLOSED event in the CEmbeddedFrame
class, can we make the Dialog peer do something upon closing? From
Java perspective, the Dialog knows about its parent, so at the peer's
level the dialog peer could simply call a method in the CEmbeddedFrame
when the dialog is closing.
--
best regards,
Anthony
On 4/9/2014 3:02 PM, mikhail cherkasov wrote:
Hi all,
please review the fix:
http://cr.openjdk.java.net/~mcherkas/8032961/jdk9/webrev.00/
for the following bug:
https://bugs.openjdk.java.net/browse/JDK-8032961
The problem is that when we create modal dialog we can't set the
whole browser as its parent window, due some limitation of browser
API.
So that means we have to emulate modal dialog behavior.
When modal dialog is opened applet reject focus events - so the
applet in
browser can not become active while modal dialog is opened.
As result we can get in situation when modal dialog is closed, but
applet is inactive
and doesn't recognize any user input.
The fix tracks closing modal dialogs and if browser active it activates
applet too.
Thanks,
Mikhail.