If you look into the extended browser info detection, you'll see the results of some JavaScript tests being submitted as a form, and saved in a session-scoped object for server-side use. Instead of using these results, you can use your own session-scoped information, and your own Wicket behavior to detect/submit your data. This behavior can be added at a page level, or added with an application-level listener, depending on what's easiest for you.
If you want to avoid the initial "if you see this..." page, you'll need to provide some defaults / assumptions for the detected properties for use in the initial page rendering. In the case of screen resolution detection, this is not a problem; just choose something conservative. You can see some details of my solution here: http://apache-wicket.1842946.n4.nabble.com/Dynamically-sized-image-td4456657.html Dan On Tue, May 1, 2012 at 7:49 PM, mlabs <mlabs....@gmail.com> wrote: > So I added a call to: > > getRequestCycleSettings().setGatherExtendedBrowserInfo(true); > > in my app.init() > > and sure enough I can now see the client's browser resolution... > > but I also see it briefly redirect to a page with some 'if you see this..' > text on it... > > Q: Is there any way to stop that showing up? > > Q: if not, is there a better way to detect the client's browser resolution? > > TIA > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/browser-resolution-info-ClientProperties-question-tp4602259.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
