QueryParameters.toFormUrlEncoded() / QueryParameters.parseForm() (backed by the internal FormUrlEncoded object) are public API, but the only test coverage is the hand-written FormUrlEncodedTest/QueryFormTest suites — there's no vendored WPT urlencoded / application/x-www-form-urlencoded / urlsearchparams corpus backing them, unlike the URL and IDNA test suites.
The behavior is very likely correct, but it's unmeasured against the standard's own conformance corpus, so the README's "Supported" label (rather than "Conformant") for this feature is honest about that gap today.
Proposal: vendor the WPT urlencoded/urlsearchparams corpora as a ratcheting suite, following the same pattern already used for the URL and IDNA corpora (Go generator under tools/, generated fixture + known-failures baseline, wired into check).
QueryParameters.toFormUrlEncoded()/QueryParameters.parseForm()(backed by the internalFormUrlEncodedobject) are public API, but the only test coverage is the hand-writtenFormUrlEncodedTest/QueryFormTestsuites — there's no vendored WPTurlencoded/application/x-www-form-urlencoded/urlsearchparamscorpus backing them, unlike the URL and IDNA test suites.The behavior is very likely correct, but it's unmeasured against the standard's own conformance corpus, so the README's "Supported" label (rather than "Conformant") for this feature is honest about that gap today.
Proposal: vendor the WPT
urlencoded/urlsearchparamscorpora as a ratcheting suite, following the same pattern already used for the URL and IDNA corpora (Go generator undertools/, generated fixture + known-failures baseline, wired intocheck).