W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > November 2012

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

From: <bugzilla@jessica.w3.org>
Date: Thu, 29 Nov 2012 04:39:49 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-20148-2532-hb3sJbP7ja@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20148

Glenn Maynard <glenn@zewt.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |glenn@zewt.org

--- Comment #1 from Glenn Maynard <glenn@zewt.org> ---
Ordering isn't lost; it's just not exposed by the "get" method.  getAll lets
you access the less common cases: repeated keys, significant ordering, and when
you have elements that aren't key=value.  (A system I've used now and then is
"http://url.com?foo/bar&x=y", where the first parameter is treated like a
path.)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 29 November 2012 04:39:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 29 November 2012 04:39:51 GMT