Can anybody comment on this? Is this a bug?
Thanks,
Alec
On Sun, Jan 22, 2012 at 11:50 AM, Alec Swan alecs...@gmail.com wrote:
The following workaround works but violates encapsulation. Why doesn't
AjaxRequestTarget.AjaxHeaderResponse class escape special XML
characters?
public void
Hi,
Yes, looks like a bug.
Please create a ticket + a quickstart.
On Tue, Jan 24, 2012 at 8:56 PM, Alec Swan alecs...@gmail.com wrote:
Can anybody comment on this? Is this a bug?
Thanks,
Alec
On Sun, Jan 22, 2012 at 11:50 AM, Alec Swan alecs...@gmail.com wrote:
The following workaround
The following workaround works but violates encapsulation. Why doesn't
AjaxRequestTarget.AjaxHeaderResponse class escape special XML
characters?
public void renderHead(IHeaderResponse response) {
String scriptToRender = scriptif (1 == 1 true)
alert('Hello!')/script;
if
Hello,
I am using Wicket 1.4.17 and have a panel which implements
IHeaderContributor as follows:
public void renderHead(IHeaderResponse response) {
response.renderString(scriptif (1 == 1 true) alert('Hello!')/script);
}
When the panel is updated as a part of AJAX request (by adding to ART)
