-
Notifications
You must be signed in to change notification settings - Fork 20.6k
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
Deprecate jQuery.trim? #4363
Comments
I think this might be a good enough reason to keep it. It'll be pretty small without the regex. |
We've deprecated |
Well, I was against deprecating that too. I wouldn't say it did a lot more than native |
That brings up another point. |
Semver mandates deprecations can only happen in minor or major bumps so it can only happen in 4.0.0 or 3.5.0 if we ever decide to release that. |
I don't have a strong feeling either way on this. Removing it won't change the file size that much but I'd actually prefer that people used the built-in methods rather than our utilities. As @timmywil says we don't actually need to remove it but could signal there are alternatives by deprecating. |
@ShashankaNataraj Sure, PRs welcome! |
Description
jQuery.trim
was useful for IE <9 and later to workaround an old Android Browser issue but we don't support that browsers anymore onmaster
. It also adds one niceity that it accepts anull
value that it turns to an empty string but that's it. Should we deprecate it?Link to test case
The text was updated successfully, but these errors were encountered: