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
Remove the onKeyPress handler from the number field as HTML5
number doesn't allow non-numeric input.
Add "TODO" test - it won't render field with a non-numeric value.
Update example with number field.
Fix bug with Form#handleEditorEvents tests running standalone -
async in qunit.
glenpike
pushed a commit
to glenpike/backbone-forms
that referenced
this issue
Dec 30, 2016
Remove the onKeyPress handler from the number field as HTML5
number doesn't allow non-numeric input.
Add "TODO" test - it won't render field with a non-numeric value.
Update example with number field.
Fix bug with Form#handleEditorEvents tests running standalone -
async in qunit.
The implementation of
editors.Number.onKeyPress
is faulty and prevents the form from being submitted by pressing the "enter" key.Currently, the newline character
\r
gets appended tonewVal
in https://github.com/powmedia/backbone-forms/blob/master/src/editors/number.js#L50, which makes thenumeric
test fail a few lines below, which in turn results in theevent.preventDefault();
call.https://jsfiddle.net/s1h0s5mm/1/
The text was updated successfully, but these errors were encountered: