URLs / subclassing JavaScript

Anne van Kesteren annevk at annevk.nl
Mon Dec 17 06:19:29 PST 2012


If down the road we want to allow for the theoretical possibility of
having all platform APIs implemented in JavaScript, we might want a
sync Object.observe. If we have types down the road as well (this
might be a bit presumptuous), URLQuery could just be a MultiMap and
whenever the MultiMap was mutated you'd update the associated URL
synchronously (and potentially do other things, such as navigating to
a URL). The latter would require synchronous change delivery. Or I
suppose some kind of subclass that changes all the manipulation
methods to also perform some kind of notification.

I guess the problems here are that a) there's no MultiMap b) there's
no types c) we want to reduce the burdon on developers for doing URL
manipulation probably without waiting for a/b, but I rather not pull a
Typed Array.

Similarly, there's an idea to expose the path of a URL as an array of
segments. Ideally this would be a type-constrained Array that when
manipulated updates the associated URL.

Oh, and by the way, I read
http://infrequently.org/2012/12/reforming-the-w3c-tag/#comment-240289
the other day. 1) In so far there would be an organisation responsible
for the URL work, it would be the WHATWG, not the W3C. 2) But really
as far as the API of URLQuery goes, that's mostly arv, TabAtkins, and
I. 3) If you have feedback on it, better to email it :-)


URLQuery: http://url.spec.whatwg.org/#urlquery


-- 
http://annevankesteren.nl/


More information about the es-discuss mailing list