- From: Brian Kardell <bkardell@gmail.com>
- Date: Tue, 12 Aug 2014 11:15:32 -0400
- To: Takeshi Yoshino <tyoshino@google.com>
- Cc: Anne van Kesteren <annevk@annevk.nl>, public-webapps@w3.org
- Message-ID: <CADC=+jfLiy8Kyw+tRTJXF24SW2ZJphw2=hkghwzDKSse8ZEZBg@mail.gmail.com>
On Aug 12, 2014 11:12 AM, "Takeshi Yoshino" <tyoshino@google.com> wrote: > > On Tue, Aug 12, 2014 at 10:55 PM, Anne van Kesteren <annevk@annevk.nl> wrote: >> >> On Tue, Aug 12, 2014 at 3:37 PM, Brian Kardell <bkardell@gmail.com> wrote: >> > If there's no really good reason to change it, least change is better IMO >> >> All I can think of is that it would be somewhat more consistent to not >> have this list and always uppercase, > > > Ideally > >> >> but yeah, I guess I'll just align >> fetch() with XMLHttpRequest. > > > Isn't it an option that we use stricter rule (all uppercase) for the newly-introduced fetch() API but keep the list for XHR? Aligning XHR and fetch() is basically good but making fetch() inherit the whitelist is a little sad. > > > > Some archaeology: > > - Blink recently reduced the whitelist to conform to the latest WHATWG XHR spec. http://src.chromium.org/viewvc/blink?view=revision&revision=176592 > - Before that, used this list ported to WebKit from Firefox's behavior http://trac.webkit.org/changeset/13652/trunk/WebCore/xml/xmlhttprequest.cpp > - Anne introduced the initial version of the part of the spec in Aug 2006 http://dev.w3.org/cvsweb/2006/webapi/XMLHttpRequest/Overview.html.diff?r1=1.12;r2=1.13;f=h > -- http://lists.w3.org/Archives/Public/public-webapi/2006Apr/0124.html > -- http://lists.w3.org/Archives/Public/public-webapi/2006Apr/0126.html > fetch should explain magic in XMLHttpRequest et all.. I don't see how it could differ in the way you are suggesting and match
Received on Tuesday, 12 August 2014 15:16:05 UTC