- From: Simon Sapin <notifications@github.com>
- Date: Sat, 02 Apr 2016 08:04:24 -0700
- To: whatwg/url <url@noreply.github.com>
Received on Saturday, 2 April 2016 15:04:52 UTC
b174f8f2170a4ce6fd4031206e0490eff2b0aa02 added > Otherwise, if tuple has a type, and tuple’s type is "file", set outputPair’s value to tuple’s value’s filename. Contrary to the general case, a filename here does not go through the "byte serializer" (or character encoding). This means that any `&` or `=` character in the name will be serialized as-is, incorrectly creating new name/value pairs when the serialized string is parsed again. Is this really intended? It’s also not clear from https://html.spec.whatwg.org/#concept-input-type-file-selected what the type of a file name is supposed to be in the first place. (Bytes vs Unicode vs WTF-16/DOMString.) --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/url/issues/109
Received on Saturday, 2 April 2016 15:04:52 UTC