Incorrect handling of windows line endings

[esetnik]

20250110171129_Advanced_Report_Writer_d0d0e030-redacted.csv

Using this file with the demo on Papa Parse:

Produces the following error:

Parsing file... File {name: '20250110171129_Advanced_Report_Writer_d0d0e030-redacted.csv', lastModified: 1736785804636, lastModifiedDate: Mon Jan 13 2025 11:30:04 GMT-0500 (Eastern Standard Time), webkitRelativePath: '', size: 68, …}
demo.js:175 Parse complete
demo.js:176        Time: 5.800000011920929 ms
demo.js:177   Row count: 2
demo.js:180      Errors: 2
demo.js:182 First error: {type: 'FieldMismatch', code: 'TooManyFields', message: 'Too many fields: expected 2 fields but parsed 3', row: 0}code: "TooManyFields"message: "Too many fields: expected 2 fields but parsed 3"row: 0type: "FieldMismatch"[[Prototype]]: Object
demo.js:236     Results: {data: Array(2), errors: Array(2), meta: {…}}
demo.js:175 Done with all files
demo.js:176        Time: 6.300000011920929 ms
demo.js:177   Row count: 2
demo.js:180      Errors: 2
demo.js:182 First error: {type: 'FieldMismatch', code: 'TooManyFields', message: 'Too many fields: expected 2 fields but parsed 3', row: 0}

This is a valid csv file with \r\n line endings.

[esetnik]

Maybe related to #1075

[esetnik]

I downgraded to v5.3.2 and the same file is working as expected. #998 Seems to be an issue with versions >5.3.2

[hermit99]

+1. Here is another simplified repo:

A	B,C
"D EF "	GH
K_	LM

Set delimiter to \t is fine, but if set delimiter to , it complains 'Trailing quote on quoted field is malformed'.

[dboskovic]

adding this to v6 release scope