Normalize line endings so we don't have validation issues on windows.

[ionelmc]

No description provided.

[aaugustin]

Could you clarify what the validation issues are?

[ionelmc]

Windows will send \r\n in the forms, instead of \n - making the hash
missmatch.

Thanks,
-- Ionel M.

On Sun, Jan 26, 2014 at 9:29 PM, Aymeric Augustin
notifications@github.comwrote:

Could you clarify what the validation issues are?

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/533#issuecomment-33327338
.

[ionelmc]

It happens at least on Google Chrome on Win8

Thanks,
-- Ionel M.

On Sun, Jan 26, 2014 at 9:31 PM, Ionel Cristian Mărieș
contact@ionelmc.rowrote:

Windows will send \r\n in the forms, instead of \n - making the hash
missmatch.

Thanks,
-- Ionel M.

On Sun, Jan 26, 2014 at 9:29 PM, Aymeric Augustin <
notifications@github.com> wrote:

Could you clarify what the validation issues are?

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/533#issuecomment-33327338
.

[aaugustin]

Oh, yes, browsers standardize newlines in inputs to \n. (That makes javascript character counters notoriously hard to get right.) I didn't know they also did this for hidden inputs.

[ionelmc]

Btw, it was a pull request not a bug report ... :-)

[aaugustin]

I know, and I started from your patch, but then I wanted to make some changes, and eventually refactored the method entirely...