I am writing some purely client-side jQuery (no AJAX). Should I be aware of jQuery-specific security holes I might inadvertently introduce for the clients?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am writing some purely client-side jQuery (no AJAX). Should I be aware of jQuery-specific security holes I might inadvertently introduce for the clients?
jQuery is a library to make native JavaScript much easier to use. The only security holes it will have are the ones introduced by the browser to any JavaScript code. These holes aren’t that common, but they’re the ones you need to look out for. The only thing jQuery might contribute is a few bugs, but it’s tested thoroughly on all common browsers.