- From: Hallvord Reiar Michaelsen Steen <hallvord@opera.com>
- Date: Thu, 30 May 2013 13:16:54 +0200
- To: "Jonas Sicking" <jonas@sicking.cc>
- Cc: "Mark S. Miller" <erights@google.com>, "Charles McCathie Nevile" <chaals@yandex-team.ru>, public-webapps <public-webapps@w3.org>, "Tyler Close" <tyler.close@gmail.com>, mjs <mjs@apple.com>, "Dirk Pranke" <dpranke@chromium.org>, ojan <ojan@chromium.org>, w3c <w3c@adambarth.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, "Ian Hickson" <ian@hixie.ch>, "Devdatta Akhawe" <dev.akhawe@gmail.com>, "art.barstow" <art.barstow@nokia.com>, nathan <nathan@webr3.org>, "John Kemp" <john@jkemp.net>, "Jungkee Song" <jungkees@gmail.com>, "Julian Aubourg" <j@ubourg.net>, "Anne van Kesteren" <annevk@annevk.nl>, ๏̯͡๏ Jasvir Nagra <jasvir@google.com>
> > Now, if you are still not convinced this is a good change my plan B is to suggest a "credentialsPolicy" property so we'll find an agreement anyway. :-) But maybe explaining that no quirky getter magic is required helps you see the proposal in a new light? > > Whatever we're doing here is going to result in a lot of confusion. > There's already lots of existing code, tutorials and documentation > that treats this property as a boolean property. At best we'd not > break existing code, but cause a mix of code/documentation which some > treats it as a boolean and others as a string. > > Hence my statement that there's no way that we can create a clean > solution while reusing the existing property. > > So my objection still stands. Creating a new property seems to have > much fewer downsides. OK then - Anne and others, what do you think about creating a new tri-state xhr.credentialsPolicy property and discouraging usage of xhr.withCredentials ? -- Hallvord R. M. Steen Core tester, Opera Software
Received on Thursday, 30 May 2013 11:17:54 UTC