[
https://issues.apache.org/jira/browse/WICKET-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15701571#comment-15701571
]
Sven Meier commented on WICKET-6056:
------------------------------------
Yes, I think this is the best we can do, without having to build a huge
framework.
Only disadvantage is that people have to deal with
BrowserInfoPage#newClientInfo() and AjaxClientInfoBehavior#newClientInfo() iff
they are using both detection methods simultaneously - which is rather unlikely.
> Improvements to browser info gathering implementation
> -----------------------------------------------------
>
> Key: WICKET-6056
> URL: https://issues.apache.org/jira/browse/WICKET-6056
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 6.21.0, 7.1.0
> Reporter: Rakesh A
> Assignee: Martin Grigorov
> Priority: Minor
> Attachments: 0001-Extra-client-info-provider-is-added.patch
>
>
> Current implementation of browser information gathering (WebClientInfo and
> related classes), is difficult to extend/customize.
> 1. Current implementation does not allow me to detect browser's touch api
> support
> 2. Wanted to use client side implementation library to detect browser
> features - like Modernizr.
> Initial discussion regarding this can be found at
> http://apache-wicket.1842946.n4.nabble.com/Regarding-Browser-Client-info-implementation-td4673024.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
