Regarding the link you sent, I also think that the current behaviour is inconsistent. I'm now not sure if we should go with \n, or \r\n, but I think we definitely should normalize this. If you are writing to files on windows, all your browsers would send \r\n over post, so the files would be generated properly, but as soon as you deploy, and the first client enters some data from OSX for example, you have a problem which you couldn't even notice before. What I'm trying to say here is that I think it's better if it was consistent, and you could catch the issue during implementation.
On Monday, November 12, 2018 at 3:58:39 PM UTC+1, Jakub Kleň wrote: