Question

After this weekend my Wicket application cannot correctly detect javascript anymore. It doesn’t work on my webhoster, on my local machine and I tested it also on another computer.

My detection script:

WebClientInfo clientInfo = (WebClientInfo)WebSession.get().getClientInfo();
    if(!clientInfo.getProperties().isJavaEnabled()){
        System.out.println("not enabled!");
        WebSession.get().setClientInfo(null);
    }

plus this in the application class:

getRequestCycleSettings().setGatherExtendedBrowserInfo(true);

I also created a wicket app from scratch, same result, no javascript detection.

While writing this I checked it in the Internet Explorer. Works fine with IE 8 + 9. Doesn’t work with FF 11.0. Wicket version is 1.5.5.

Anyone can confirm this behavior? (possible JIRA-worthy…)

UPDATE: I found the cause of this behavior. isJavaEnabled checks if Java (not Javascript) is enabled. Firefox (silently) blocked the Java plugin on April 2nd, therefore no javaEnabled property set: https://addons.mozilla.org/en-US/firefox/blocked/p80. Cumbersome.

Answer 1

Likely this never worked, and the fact that it seemed to was dumb luck.

Looking at the javadocs for ClientProperties.isJavaEnabled(), it returns the client’s navigator.javaEnabled property, which reflects whether Java is enabled, not JavaScript.

Java != JavaScript.