Summary: | Inconsistent/lazy encoding of URL.searchParams | ||
---|---|---|---|
Product: | WebKit | Reporter: | Jim Heising <jheising> |
Component: | WebCore JavaScript | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | achristensen, ap, jheising, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Description
Jim Heising
2019-11-12 14:47:53 PST
It seems like one solution would be to call updateURL() (https://trac.webkit.org/browser/webkit/trunk/Source/WebCore/html/URLSearchParams.cpp#L139) during object construction. Our behavior here matches the behavior of Chrome and Firefox and the URL specification. For whatever reason, https://url.spec.whatwg.org/#concept-urlencoded-byte-serializer uses a different set than https://url.spec.whatwg.org/#query-state step 5. Because the behavior of all browsers agrees, you're going to have a hard time changing the specification. |