W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2012

[Bug 20148] URLQuery interface does not handle query parameter ordering

From: <bugzilla@jessica.w3.org>
Date: Fri, 30 Nov 2012 19:41:43 +0000
To: public-webapps@w3.org
Message-ID: <bug-20148-2927-CZHvgOuXgi@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20148

Anne <annevk@annevk.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #8 from Anne <annevk@annevk.nl> ---
FYI http://url.spec.whatwg.org/#interface-urlquery now reflects the final
design. set() only changes a single value, the first. If you want to effect
multiple name-value pairs you will have to use a combination of delete() and
append().

get() returns the first value for a given name, getAll() returns all values for
a given name.

You might want to have a look at https://github.com/annevk/url for a URL parser
in JavaScript. I haven't updated it to match the specification yet though, I
wrote it to base the specification on.

I'm going to mark this bug WORKSFORME. Specific bugs for serialization and
comparison APIs are welcome provided there are good enough use cases. (There's
a vague plan of adding URL comparison to the API and serialization might make
sense for URLQuery I suppose, but it's not really concrete at this stage.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 30 November 2012 19:41:46 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:56 GMT