New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion: Handle data length reductions #16
Comments
Adding a 2nd OR clause covers the above cases: (Sorry, new to Git, so I apologize if there was some other way I was supposed to submit a suggestion!) |
Thanks, this really helped me! For others: if ((value.length >= options.captureLength && value.toUpperCase() != timer.text)
|| (override && value.length >= options.captureLength)
|| (value.length < options.captureLength && timer.text.length >= options.captureLength)) Also, you probably want to set |
_scoman81_ Thank you for describing the issue. I've had a few other requests for this fix but they always seemed to describe the issue in a manner that made me think they should just set the _captureLength_ to 1. With your description I was finally able to understand the issue. I'll get your fix in shortly. Thanks. |
+1 for this important fix. |
This line makes the empty state work. || (value.length === 0 && timer.text.length > 0) |
There are two common cases (actually two derivatives of the same case, that just feel different) that would be nice to see handled by this plugin:
These are really both the same case: when the data length decreases from over the captureLength setting, to under the captureLength setting.
The text was updated successfully, but these errors were encountered: