W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2014

Re: Fetch API

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 29 May 2014 12:37:38 -0700
Message-ID: <CAAWBYDAeMWoT8eLSes=7rZtEW1vtzCfKP50xrk6BcFwZAi_yEQ@mail.gmail.com>
To: Tobie Langel <tobie.langel@gmail.com>
Cc: Marcos <marcos@marcosc.com>, WebApps WG <public-webapps@w3.org>, Jonas Sicking <jonas@sicking.cc>, public-script-coord <public-script-coord@w3.org>, Jungkee Song <jungkee.song@samsung.com>, Anne van Kesteren <annevk@annevk.nl>, Alex Russell <slightlyoff@google.com>, Yehuda Katz <wycats@gmail.com>, Joshua Bell <jsbell@chromium.org>, Jake Archibald <jaffathecake@gmail.com>
On Thu, May 29, 2014 at 8:10 AM, Tobie Langel <tobie.langel@gmail.com> wrote:
> On Thu, May 29, 2014 at 4:58 PM, Marcos <marcos@marcosc.com> wrote:
>>
>>
>> > enum RequestMode { "same-origin", "tainted cross-origin", "CORS",
>> > "CORS-with-forced-preflight" };
>>
>> I think these are badly named (even though they use the names used in HTML
>> and Fetch). It's going to be annoying to type these out for developers.
>>
>> I would change them to:
>> enum RequestMode { "same-origin", "cors", "cors-tainted", "cors-preflight"
>> };
>
> I like those better.
>
> We want consistency with lowercasing or uppercasing cors/CORS in enums,
> though.

Yes.  Lowercasing always, please.

~TJ
Received on Thursday, 29 May 2014 19:38:33 UTC

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