[
https://issues.apache.org/jira/browse/WICKET-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergiy Barlabanov updated WICKET-3912:
--------------------------------------
Attachment: quickstart.zip
> SCRIPT tags in Ajax-Response are not evaluated in Chrome
> --------------------------------------------------------
>
> Key: WICKET-3912
> URL: https://issues.apache.org/jira/browse/WICKET-3912
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC5.1
> Environment: Mac OS X 10.6.6, Chrome 12, Java 6, Tomcat 6
> Reporter: Sergiy Barlabanov
> Attachments: quickstart.zip
>
>
> if a JavaScript script tag is added to AjaxRequestTarget (by Behavior via
> JavaScriptUtils.writeJavaScript), it is not evaluated on Chrome browser.
> While debugging through wicket-ajax.js, it turns out, that
> replaceOuterHtmlSafari function is not called for Chrome, but the Gecko
> version gets executed instead (fall to "} else /* GECKO */ {" in
> Wicket.replaceOuterHtml). And the Gecko version does not do any special
> handling of SCRIPT tag, since Firefox does execute SCRIPT nodes added
> dynamically to the DOM.
> This behavior occurs since 1.5-RC5.1.
> There is a quickstart webapp attached to this ticket. HomePage contains a
> Label with Behavior attached and an AjaxLink. Behavior add a JavaScript
> showing alert message. It is shown once the page is loaded and once the ajax
> link is clicked. In Chrome there is not alert message after clicking the ajax
> link.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
