- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Sat, 1 Jun 2013 09:12:16 +0100
- To: Hallvord Reiar Michaelsen Steen <hallvord@opera.com>
- Cc: ๏̯͡๏ Jasvir Nagra <jasvir@google.com>, Julian Aubourg <j@ubourg.net>, Jungkee Song <jungkees@gmail.com>, John Kemp <john@jkemp.net>, nathan <nathan@webr3.org>, "art.barstow" <art.barstow@nokia.com>, Devdatta Akhawe <dev.akhawe@gmail.com>, Ian Hickson <ian@hixie.ch>, "Tab Atkins Jr." <jackalmage@gmail.com>, w3c <w3c@adambarth.com>, ojan <ojan@chromium.org>, Dirk Pranke <dpranke@chromium.org>, mjs <mjs@apple.com>, Tyler Close <tyler.close@gmail.com>, public-webapps <public-webapps@w3.org>, Charles McCathie Nevile <chaals@yandex-team.ru>, "Mark S. Miller" <erights@google.com>, Jonas Sicking <jonas@sicking.cc>
On Thu, May 30, 2013 at 1:30 PM, Hallvord Reiar Michaelsen Steen <hallvord@opera.com> wrote: > So creating a new tri-state property in the XHR spec should also simplify integration with the Fetch spec. Agreed. The question is, if we take it as a given that we're going to get a new API (that uses futures, deals with tainted requests, etc.) is it worth expanding the older API too? -- http://annevankesteren.nl/
Received on Saturday, 1 June 2013 08:12:43 UTC