> You probably still have to do: > > getRequestCycleSettings().setGatherExtendedBrowserInfo(true); > > in your application's init method.
Maybe a little explanation wouldn't hurt here :) By default, IRequestCycleSettings gatherExtendedBrowserInfo setting is false, resulting in the ClientProperties object to be initialized from just the user agent string that the browser sends with the request. This is ok for basic stuff, but for most interesting stuff, you really need some Javascript to investigate the browser and push that answer back to you. If you set the gatherExtendedBrowserInfo property to true, Wicket will do a sneaky redirect to a page that does this investigating. That page will gather the info a return to the server trying several methods (for e.g. in case Javascript is not supported). After that, the original request will be handled again (literally again, not from the point it was left) and the client properties with extended info will be available for you. Eelco ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
