[WICKET-3781] Differentiate Google Chrome from Safari in wicket-xyz.js

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5-RC4
• Fix Version/s: 1.5-RC5
• Component/s: wicket
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Martin Tzvetanov Grigorov
• Created: 09/Jun/11 12:49
• Updated: 13/Jun/11 15:16
• Resolved: 13/Jun/11 15:16

Description

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.