-
Bug
-
Resolution: Fixed
-
P3
-
fx2.0
Tested build #120 : http://jfx.sfbay.sun.com/hudson/job/presidio-deploy-scrum/label=windows-i586-14/lastSuccessfulBuild/artifact/artifacts/bundles/release/javafx-2.0-beta-windows-i586.exe
Due to securitry concerns key events has been diasbled when application/applet runs in full screen mode( Exceptions are
SPACE, TAB and ESC ) But this behavior is too restrictive fr signed applications and needs to be revisited
Steps to reproduce:
1) Try to load following applet
http://sqeweb.us.oracle.com/deployment2/jitu/latest_ws_test/6/deployment/src/javafx/fxfeaturesTest/fxfeaturesTest/html/FullscreenTextSignedTest.html
2) Accept security pop-up and click button to go into full screen mode.
3) Once in full screen mode, try to type something into the text area. If key events are ignore then bug is reproduced
Due to securitry concerns key events has been diasbled when application/applet runs in full screen mode( Exceptions are
SPACE, TAB and ESC ) But this behavior is too restrictive fr signed applications and needs to be revisited
Steps to reproduce:
1) Try to load following applet
http://sqeweb.us.oracle.com/deployment2/jitu/latest_ws_test/6/deployment/src/javafx/fxfeaturesTest/fxfeaturesTest/html/FullscreenTextSignedTest.html
2) Accept security pop-up and click button to go into full screen mode.
3) Once in full screen mode, try to type something into the text area. If key events are ignore then bug is reproduced
- relates to
-
JDK-8119438 After the stage is set to fullscreen and then set to normal, the components inside the stage cannot read the keyboard input anymore
-
- Closed
-