27596 2014-12-12 18:14:52 +0000 Need a better story for searchParams and URLSearchParams 2015-08-14 09:32:50 +0000 1 1 1 Unclassified WHATWG URL unspecified All All RESOLVED FIXED P2 normal Unsorted 1 annevk annevk crimsteam d erik.arvidsson mamacdon MattN+w3 mike rubys sideshowbarker+urlspec oldest_to_newest 116232 0 annevk 2014-12-12 18:14:52 +0000 The tentative plan is to make searchParams readonly and the relationship 1:1. However, for Location we need something more complicated due to Location's insanity. Possible ideas for Location's searchParams and URLSearchParams: 1) Not have it 2) Scope lifetime to document (though how does that actually work if you set it for a prior document?) 3) Copy Location's security model (seems way mad) 4) Create an immutable variant Some background: https://bugzilla.mozilla.org/show_bug.cgi?id=1105677 116233 1 d 2014-12-12 19:08:56 +0000 I like the idea of having .searchParams only return the same object until a navigation occurs, or possibly until an origin change occurs, as per https://bugzilla.mozilla.org/show_bug.cgi?id=1082734. People in that thread seem to prefer removing it entirely though; I'm not sure if there's a problem with the changing-return-value idea, or if they just find it too complicated. An alternate approach that seems OK-ish would be to remove .searchParams and add .parseSearchParams(). Then URLSearchParams no longer becomes something that auto-updates its associated url objects, but instead just an in-memory data structure for application/x-www-form-urlencoded manipulation. User code might then look like var searchParams = myURL.parseSearchParams(); searchParams.set('foo', 'bar'); myURL.search = searchParams.toString(); (You could also consider at this point renaming URLSearchParams to FormURLEncodedParams or something else to emphasize its general-purpose nature.) 120990 2 annevk 2015-06-15 13:52:46 +0000 Solution 4 from comment 0 does not actually work. For now I'm going to specify 1 since I'm not sure how to tackle this for Location. Making it readonly will have to happen separately. 120991 3 annevk 2015-06-15 14:20:42 +0000 https://github.com/whatwg/url/commit/3a5e8086aff2fe3baa57fcebd1795a16de4f5d16 puts searchParams on its own interface. HTML still needs updating to add it to HTMLAreaElement and HTMLAnchorElement, but not Location. 121211 4 annevk 2015-06-18 09:58:59 +0000 (In reply to Anne from comment #2) > Making it readonly will have to happen separately. Mostly waiting for https://bugzilla.mozilla.org/show_bug.cgi?id=1174731 to be fixed in Gecko to do that. 121473 5 annevk 2015-06-25 15:24:25 +0000 That is fixed now, will update the specification next week I think. 122608 6 annevk 2015-08-14 09:32:50 +0000 https://github.com/whatwg/url/commit/0fdcfbcc58f713d3d804a0cbbe6c1d0cadab2962