Ubuntu FF3 6u14b02deployment plugin not available -> plugin2 not detected
Java Deployment toolkit: Java: 1.6.0
JavaFX deployment toolkit: 1.6.0_14-ea
mime types: Java: 1.6.0_10
Windows XP FF3:deployment plugin available -> plugin2 detected
Java Deployment toolkit: Java: 1.6.0_14
JavaFX deployment toolkit: 1.6.0_14-ea
mime types: Java: 1.6.0_14
Windows XP IE6:deployment plugin available -> plugin2 detected
Java Deployment toolkit: Java: 1.6.0_14
JavaFX deployment toolkit: 1.6.0
mime types: <empty>
Windows XP Google Chrome:deployment plugin not available -> plugin2 not detected
Java Deployment toolkit: Java: 1.6.0
JavaFX deployment toolkit: 1.6.0_14
mime types: 1.6.0_14
If it wasn't because of the fact that we get a f* icon and a baloon every time the launch the VM (who on earth ever decided that, moronic) - it'd be best to launch an VM using the applet tag and just query the VM.
this is what the jfx dt actually should do as fallback mode. it even uses cookies to do it only once. I helped to fix a bug in the jfx dt but i don't know if they are already integrated in the public script.
Matzon and everyone with a not working javafx dt, could you check out this page (it uses a different version of the script):
http://jim.campanell.com/sun/JavaVersionDetector.html@java script experts, is it possible to use two versions of the same script on the same page without conflicts?