- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Thu, 30 May 2013 12:28:34 +0100
- To: Hallvord Reiar Michaelsen Steen <hallvord@opera.com>
- Cc: Jonas Sicking <jonas@sicking.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>, ๏̯͡๏ Jasvir Nagra <jasvir@google.com>
On Thu, May 30, 2013 at 12:16 PM, Hallvord Reiar Michaelsen Steen <hallvord@opera.com> wrote: > OK then - Anne and others, what do you think about creating a new tri-state xhr.credentialsPolicy property and discouraging usage of xhr.withCredentials ? I think I'd prefer removing the constructor flag and leaving new features to the API for Fetch. Also, we still need to nail down the details of withCredentials. Questions raised in http://lists.w3.org/Archives/Public/public-webapps/2013AprJun/0499.html have gone without conclusive answers. -- http://annevankesteren.nl/
Received on Thursday, 30 May 2013 11:29:09 UTC