[
https://issues.apache.org/jira/browse/WICKET-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov resolved WICKET-3781.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.5-RC5
> Differentiate Google Chrome from Safari in wicket-xyz.js
> --------------------------------------------------------
>
> Key: WICKET-3781
> URL: https://issues.apache.org/jira/browse/WICKET-3781
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-core
> Affects Versions: 1.5-RC4
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Fix For: 1.5-RC5
>
> Attachments: wicket-3781.patch
>
>
> Currently Google Chrome is treated as Safari in wicket-ajax.js and
> wicket-event.js.
> This causes Wicket.replaceOuterHtmlSafari() to be used while Chrome supports
> Range and ContextualFragment like Gecko browsers.
> The special code in replaceOuterHtmlSafari() is for older versions of Safari
> but it is hard to test, so improvements in this area for Safari 5 will be
> done when Wicket Ajax starts use some JS library.
> This change is a bit risky because until now Chrome was treated as Safari and
> we all tested this behavior but I tested all Ajax examples in wicket-examples
> and my application and everything seems to be OK.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
