You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on Mottie's example I introduced usePreview: false
which leads to the method visible not being executed. See here. I would have expected that once the keyboard is shown, keys like space, accept, etc. are disabled.
Why does usePreview has an influence on the visible method?
The text was updated successfully, but these errors were encountered:
Hmm, thanks for reporting this problem... it looks like bug in that when usePreview is false, the callback bindings are removed because of name-spacing. I'll have that patch available in the master branch here shortly.
Alternatively, binding to the visible event would have worked either way (demo)
$('#keyboard').on('visible change',function(e,keyboard){// do something}).keyboard({usePreview: false});
Oh, sorry... I should have bound to "keyboardChange" which is an event that is fired with any change to the content versus "change" which is only fired, on the original element, when the content has been accepted or canceled (docs & demo).
$('#keyboard').on('visible keyboardChange',function(e,keyboard){// do something}).keyboard({usePreview: false});
Hi,
Based on Mottie's example I introduced
usePreview: false
which leads to the method visible not being executed. See here. I would have expected that once the keyboard is shown, keys like space, accept, etc. are disabled.
Why does usePreview has an influence on the visible method?
The text was updated successfully, but these errors were encountered: