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.
This is an offshoot of this question: Chrome counts characters wrong in textarea with maxlength attribute
In that question it was found that Javascript counts carriage returns are one character when in fact it is two (\r\n), why is that?
Test Fiddle: http://jsfiddle.net/maniator/E527z/
For reasons unknown, jQuery always converts all newlines in the value of a
<textarea>to a single character. That is, if the browser gives it\r\nfor a newline, jQuery makes sure it’s just\nin the return value of.val(). (Actually the reason probably isn’t “unknown”; it’s probably to normalize the results across browsers, because IE reports newlines as being 2 characters long.)Chrome and Firefox both count the length of
<textarea>tags the same way for the purposes of “maxlength”.However, the HTTP spec insists that newlines be represented as
\r\n. Thus, jQuery, webkit, and Firefox all get this wrong. When the field is posted, webkit and Firefox correctly add the newlines!The upshot is that “maxlength” on
<textarea>tags is pretty much useless if your server-side code really has a fixed maximum size for a field value.Edit This is still an issue in 2015 – at least on Chrome 45.0.2454 and IE 11.0.9600.