W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2014

Re: XMLHttpRequest: uppercasing method names

From: Matthew Robb <matthewwrobb@gmail.com>
Date: Tue, 9 Sep 2014 22:43:09 -0400
Message-ID: <CAAngBgij-NHU=z_EoD=GAAnvLK_n-8sV_63LtDrzOidsmOgKug@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: Brian Kardell <bkardell@gmail.com>, public-webapps <public-webapps@w3.org>, Takeshi Yoshino <tyoshino@google.com>
I think it would be super useful if there were some standard built in
functions for selecting properties. I would benefit greatly from being able
to look up a prop with case insensitivity. I guess you COULD do this with
proxies but I have to imagine it could be done faster if built in.

It wouldn't be awful if I could query a nested object structure using
something like css selecting or something like xpath but for us.
On Aug 12, 2014 12:51 PM, "Anne van Kesteren" <annevk@annevk.nl> wrote:

> On Tue, Aug 12, 2014 at 6:10 PM, Takeshi Yoshino <tyoshino@google.com>
> wrote:
> > On Wed, Aug 13, 2014 at 1:05 AM, Anne van Kesteren <annevk@annevk.nl>
> wrote:
> >> Well fetch() will never be able to explain synchronous fetches. But in
> >> general I agree that it would be sad if XMLHttpRequest could do more
> >> than fetch(). Per bz it seems we should just align fetch() with
> >> XMLHttpRequest and call it a day.
> >
> > wfm
> >
> > seems Safari is also going to be compliant to the latest spec.
> > https://bugs.webkit.org/show_bug.cgi?id=134264
>
> That's great! fetch() and XMLHttpRequest are now aligned. They both
> use a "normalize" concept defined in Fetch.
>
>
> --
> http://annevankesteren.nl/
>
>
Received on Wednesday, 10 September 2014 02:43:36 UTC

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