Re: [whatwg/url] Proposal of .toString({ concise: true }) for nicer output with empty values (#469)

> wouldn't the most compatibility between systems naturally be attained by everyone aligning on https://url.spec.whatwg.org/#application/x-www-form-urlencoded?

Thanks for the reference.  Under these encoding rules, it sounds like a name-value pair terminated by a `=` character (e.g. `a=`) and a standalone name (e.g. `a`) both parse to an empty byte sequence (e.g. empty string), according to the rules in section 5.1, steps 3.2 and 3.3.

That would raise a similar concern, making it challenging for developers and applications to unambiguously distinguish between null and empty string values during serialization and deserialization operations.

Although any decision made here could arguably *also* apply to `x-www-form-urlencoded`, perhaps it'd be easiest (in terms of minimizing fragmentation of discussion) to focus on one area of the standard to begin with, and then later discuss whether any changes should also apply elsewhere?

-- 
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/469#issuecomment-627194662