- From: <bugzilla@jessica.w3.org>
- Date: Tue, 20 Nov 2012 12:45:56 +0000
- To: public-script-coord@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20019 Priority: P2 Bug ID: 20019 CC: mike@w3.org, public-script-coord@w3.org Assignee: cam@mcc.id.au Summary: Support subclassing ES6 Map QA Contact: public-webapps-bugzilla@w3.org Severity: normal Classification: Unclassified OS: All Reporter: annevk@annevk.nl Hardware: PC Status: NEW Version: unspecified Component: WebIDL Product: WebAppsWG Context: http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Nov/thread.html#msg220 URLQuery constraints: URLQuery represents an ordered list of name/value pairs and within that list duplicate names can occur. URLQuery API propopal: * new URLQuery(object) creates an ordered list of name/value pairs. We might want to support sequenced values in the object so you can create duplicate names. * get(name) gets the value of the first matching name. * getAll(name) gets all values. * set(name, values) gets the matching items from the list and from that new list replaces their values one by one. If there's values left, appends new items to the list. If there's too few values, removes items from the list. * add(name, values) ads new name/value pairs to the list. * has(name) same semantics. * delete(name [, value]) deletes all of name, or only removes those with a matching value. name/value are also constrained in what they can contain. Percent-encoding happens for both. In addition URLQuery directly manipulates the query string of the associated URL object. (I'm not entirely happy with the set() semantics above. Maybe initially we should only support setting a single value and require add() for duplicates?) -- You are receiving this mail because: You are on the CC list for the bug.
Received on Tuesday, 20 November 2012 12:46:08 UTC