Sorry, but I wasn't looking for a solution. I have no way to reproduce the
issue. It seemed like you were making good progress in your other thread.
However, if you're able to create a quickstart that can reliably reproduce
the issue, the core devs will certainly be interested in taking a look
Hi Jeremy,
did you find a solution as we've had the problem for a long time now
and more and more people are reporting it as they move over to FF and
Chrome?
On Tue, Jan 25, 2011 at 3:39 AM, Jeremy Thomerson
jer...@wickettraining.com wrote:
Perhaps this thread will help:
please attach a quickstart that reproduce it to a jira issue.
-igor
On Sun, Jan 23, 2011 at 10:40 PM, Jeffrey Schneller
jeffrey.schnel...@envisa.com wrote:
Got an odd issue occurring where the Ajax Response xml is showing in the
browser rather than modifying the DOM of the page as it usually
Perhaps this thread will help:
http://apache-wicket.1842946.n4.nabble.com/Ajax-response-render-as-source-in-the-browser-tt3028722.html
--
Jeremy Thomerson
http://wickettraining.com
*Need a CMS for Wicket? Use Brix! http://brixcms.org*
On Mon, Jan 24, 2011 at 9:48 AM, Igor Vaynberg
Got an odd issue occurring where the Ajax Response xml is showing in the
browser rather than modifying the DOM of the page as it usually does.
The scenario is the following:
My Login page is abstract and has an abstract method called
onLoginSuccess.
When the login is successful we call
