HTML: search setter always uses UTF-8

We changed the Location search setter at some point to no longer pass the encoding argument, but it seems that for <a> and <area> the specification always required UTF-8.
web-platform-tests · Sep 4, 2023 · 8236142 · 8236142
1 parent 8a2a07f
commit 8236142
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/html/infrastructure/urls/resolving-urls/query-encoding/resources/resolve-url.js b/html/infrastructure/urls/resolving-urls/query-encoding/resources/resolve-url.js
@@ -392,9 +392,9 @@ onload = function() {
       elm.href = input_arr[0];
       elm.search = '?' + input_arr[1];
       var got_href = elm.getAttribute('href');
-      assert_true(got_href.indexOf(expected_current) > -1, 'href content attribute ' + msg(expected_current, got_href));
+      assert_true(got_href.indexOf(expected_utf8) > -1, 'href content attribute ' + msg(expected_utf8, got_href));
       var got_search = elm.search;
-      assert_true(got_search.indexOf(expected_current) > -1, 'getting .search '+msg(expected_current, got_search));
+      assert_true(got_search.indexOf(expected_utf8) > -1, 'getting .search '+msg(expected_utf8, got_search));
     }, '<'+tag+'>.search');
   }
   'a, area'.split(', ').forEach(function(str) {