Bug 185419 - location.search doesn't use document encoding
Summary: location.search doesn't use document encoding
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar, WPTImpact
Depends on:
Blocks:
 
Reported: 2018-05-08 04:54 PDT by Anne van Kesteren
Modified: 2022-09-22 08:31 PDT (History)
8 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anne van Kesteren 2018-05-08 04:54:31 PDT
Unlike all other location setters it seems .search is somewhat special. That's not per standard. See https://github.com/w3c/web-platform-tests/pull/10891 for tests.
Comment 1 Sam Weinig 2018-05-08 16:22:40 PDT
This is probably related to https://bugs.webkit.org/show_bug.cgi?id=161176.
Comment 2 Ahmad Saleem 2022-09-17 00:16:11 PDT
Safari Technology Preview 153 and Chrome Canary 1107 both fail two tests from below:

https://wpt.fyi/results/html/infrastructure/urls/resolving-urls/query-encoding?label=master&label=experimental&aligned&view=subtest&q=query-encoding%2Flocation.sub.html
Comment 3 Radar WebKit Bug Importer 2022-09-19 09:46:10 PDT
<rdar://problem/100126446>
Comment 4 Anne van Kesteren 2022-09-22 04:31:46 PDT
I filed https://github.com/whatwg/html/issues/8308 to see if this is something we should change in the HTML Standard instead. Just using UTF-8 in more place has its benefits.
Comment 5 Anne van Kesteren 2022-09-22 08:31:39 PDT
Tests are updated in https://github.com/web-platform-tests/wpt/pull/36019 and specification in https://github.com/whatwg/html/pull/8309.

This is now a feature so this is INVALID.