Hi,
I agree, while typing 'change' is not fired. But 'inputchange' is. (it's an
implementation of Wicket, its not an native browser event)
So I refined my used case and my problem appears on 'number' text field,
when the user uses the arrows to increment or decrement the value: both
events are
'inputchange' is 'input' for non-IE browsers and cut/paste for IE
If just 'change' does the job then use
AjaxFormComponentUpdatingBehavior(change).
We have to improve the javadoc of OnChangeAjaxBehavior
On Dec 20, 2014 2:13 PM, guillaume.mary guillaume.m...@interview-efm.com
wrote:
Hi,
I
Hi,
On Wed, Dec 17, 2014 at 12:26 PM, guillaume.mary
guillaume.m...@interview-efm.com wrote:
Hi all,
With WICKET-5711 OnChangeAjaxBehavior now listen both change and
inputchange on TextField. Hence when you type in the TextField, the
behavior is called twice because both events are fired
Hi all,
With WICKET-5711 OnChangeAjaxBehavior now listen both change and
inputchange on TextField. Hence when you type in the TextField, the
behavior is called twice because both events are fired by the browser. It's
the same problem as WICKET-5603 but applied to TextField for all browsers
