W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2013

Re: URLQuery / FormData

From: Rick Waldron <waldron.rick@gmail.com>
Date: Mon, 9 Sep 2013 13:35:35 -0400
Message-ID: <CAHfnhfq8JGn3GEdgs2NeZHP=mc=AyTjCxRAo43ebT7a6h2xDQA@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: "public-script-coord@w3.org" <public-script-coord@w3.org>
On Mon, Sep 9, 2013 at 7:30 AM, Anne van Kesteren <annevk@annevk.nl> wrote:

> We had a discussion here once before I think about a good
> representation for an ordered list of name/value pairs (i.e. allows
> duplicate names). In particular this is what <form> represents and
> therefore quite important.
> http://url.spec.whatwg.org/#interface-urlquery has an API, but looking
> over it now it's not really consistent in how get/set/delete works.
> My current thinking is to update URLQuery as follows:
> * get(name) -- always returns an array, with ES6 destructering this
> should be fine

Excellent! I was concerned that my explanation at the last tc-39 meeting
wasn't sufficiently convincing enough :)

* append(name, value) -- always appends to the end
> * delete(name) -- always removes all
> * has(name) -- same as now
> I'll leave out set() for now.

This makes sense, and append() covers the most common case anyway.

> Since it's a list I don't think item count should be called size, but
> rather length. However, maybe we don't need that for now either.
> The object should also support iteration. Waiting for that to get
> implemented in browsers and become more stable.

Agreed (to both)

Received on Monday, 9 September 2013 17:36:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:18 UTC