Thanks Maxim Solodovnik.
On Thu, Oct 9, 2014 at 12:33 PM, Maxim Solodovnik solomax...@gmail.com
wrote:
I also noticed this issue in our project,
Will try to take a look at it
On 9 October 2014 07:33, MadasamySankarapandian madas...@mcruncher.com
wrote:
Thankyou very much for yours reply.
IndicatingAjaxButton is nice. But I need one more step: I need the
button to be disabled during submission.
Mystic Coders indicated a solution
http://www.mysticcoders.com/blog/disabling-an-ajax-submit-button/, but
that doesn't seem to work with Wicket 7.
Some have filed bugs to Wicket
@Paul, @Martin
Select2Choice sets back its value
to getWebRequest().getRequestParameters().getParameterNames()
in renderInitializationScript method [1]
It seems like JS code like: $(#country1).select2(data, null); can be
executed on clear input, but this seems to be workaround
I'm not sure why
Additionally select2 seems to need to be forked to wicketstuff to be fixed,
should I do this?
On 10 October 2014 00:49, Maxim Solodovnik solomax...@gmail.com wrote:
@Paul, @Martin
Select2Choice sets back its value
to getWebRequest().getRequestParameters().getParameterNames()
in
Hi,
Recently I've added integration for
http://msurguy.github.io/ladda-bootstrap/ to
https://github.com/l0rdn1kk0n/wicket-bootstrap.
It was as simple as these two lines:
On 10/9/2014 1:21 PM, Martin Grigorov wrote:
...
It was as simple as these two lines:
One of the reasons I chose Wicket for my client's project was that I
expected that at this level of maturity Wicket would support the most
common use cases . (Disabling a submission button during submission is
one of the most common use cases I can think of.)
Let me first say that