-
Bug
-
Resolution: Fixed
-
P3
-
fx2.0
Firefox users don't see the FX applet loaded after following DTFX flow to install FX runtime. It is pretty confused to them as they end up at the JavaFX 2.0 is required to view this content.
The issue is very specific to Firefox browser (as the correct behavior is seen with IE, Chrome)
*** Tested Configurations:
- x86 XP(sp3), Vista(sp2)
- jre7-fcs
- DTFX (deploy-scrum/b265)
- FF 5, FF 6
*** Steps to reproduce:
0) Install jre 7-fcs
1) Make sure no FX run time on the system
2) Using Firefox to invoke DT-enable FX applet
http://jfx.us.oracle.com/hudson/view/Presidio/job/presidio-deploy-scrum/265/label=windows-i586-14/artifact/artifacts/apps/experiments/BrickBreaker.html
3) DT flow kicked in- Following the instruction to install JavaFX 2.0 runtime all the way to the end
4) Click 'Close" button from Java FX 2.0 Setup Complete dialog
If you end up with the same page you started "JavaFX 2.0 is required to view this content" and not BrickBreaker applet loaded then the issue is reproducible
It is so confusing to Firefox users as they don't see the Browser Restart Required message at all. The correct behavior is noticed with IE abd Chrome
The issue is very specific to Firefox browser (as the correct behavior is seen with IE, Chrome)
*** Tested Configurations:
- x86 XP(sp3), Vista(sp2)
- jre7-fcs
- DTFX (deploy-scrum/b265)
- FF 5, FF 6
*** Steps to reproduce:
0) Install jre 7-fcs
1) Make sure no FX run time on the system
2) Using Firefox to invoke DT-enable FX applet
http://jfx.us.oracle.com/hudson/view/Presidio/job/presidio-deploy-scrum/265/label=windows-i586-14/artifact/artifacts/apps/experiments/BrickBreaker.html
3) DT flow kicked in- Following the instruction to install JavaFX 2.0 runtime all the way to the end
4) Click 'Close" button from Java FX 2.0 Setup Complete dialog
If you end up with the same page you started "JavaFX 2.0 is required to view this content" and not BrickBreaker applet loaded then the issue is reproducible
It is so confusing to Firefox users as they don't see the Browser Restart Required message at all. The correct behavior is noticed with IE abd Chrome