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
{{ message }}
This repository has been archived by the owner on Mar 12, 2020. It is now read-only.
I don't know if this is related to issue 98 but although my regular expression only allows ^[A-z0-9]{3,30}$ putting a trailing space doesn't cause the field to become invalidated, i.e. 'foo bar' causes a match error, but not 'foobar '.
The text was updated successfully, but these errors were encountered:
Thanks for the report. You found a bug. The plugin calls $.trim() on field values before it validates them. This was originally added to prevent whitespace-filled fields from being considered valid by the required validator, but now it's being applied too broadly. Additionally, there was a recent addition to the plugin to prevent fields from re-running their validators if their value hasn't changed. In this case, the field values are being compared after the trim so the plugin thinks the field has not changed.
Either the trim needs to be more deliberately placed or I need to get rid of the problematic optimization altogether.
I don't know if this is related to issue 98 but although my regular expression only allows
^[A-z0-9]{3,30}$
putting a trailing space doesn't cause the field to become invalidated, i.e. 'foo bar' causes a match error, but not 'foobar '.The text was updated successfully, but these errors were encountered: