Hi there guys,
When I get an issue with Ajax that generates a report, as below (i.e. with tons
of errors.) The Ajax Debug Window 'dances' for ages... it also slows the
browser down to almost nothing, and while it 'dances' is almost un-clickable.
Is there any way to solve this?
Cheers,
Col.
Call the method component's setOutputMarkupId(true);
feedbackPanel.setOutputMarkupId(true);
see
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/Component.html#setOutputMarkupId(boolean)
François
On Tue, Apr 16, 2013 at 9:20 AM, Colin Rogers
Hi,
On Tue, Apr 16, 2013 at 10:20 AM, Colin Rogers
colin.rog...@objectconsulting.com.au wrote:
Hi there guys,
When I get an issue with Ajax that generates a report, as below (i.e. with
tons of errors.) The Ajax Debug Window 'dances' for ages... it also slows
the browser down to almost
. And they are difficult and frustrating to fix with an
overly enthusiastic dancing debug window...! I'm thankful it doesn't come with
sound effects... ;)
Cheers,
Col.
-Original Message-
From: francois meillet [mailto:francois.meil...@gmail.com]
Sent: 16 April 2013 17:29
To: users@wicket.apache.org
' components. When refactoring
these components, and consequently causing errors, bucket loads of Ajax
errors can potentially be raised. And they are difficult and frustrating to
fix with an overly enthusiastic dancing debug window...! I'm thankful it
doesn't come with sound effects... ;)
File
