- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Tue, 29 Jul 2014 11:31:58 +0200
- To: Ian Hickson <ian@hixie.ch>
- Cc: WebAppSec WG <public-webappsec@w3.org>
On Mon, Jul 28, 2014 at 8:33 PM, Ian Hickson <ian@hixie.ch> wrote: > An element can generate a fetch with no JS involved at all. So can a > navigation. Both of those are likely to happen before any fetch that > involves JS execution. Sure. > We have a non-JS present. JS is optional in browsers. Some don't have it > at all. We will certainly have a non-JS future, given the work being done > by multiple browser vendors to provide near-machine-code solutions (for > example, PNaCl and asm.js). asm.js still has the same runtime. > It's hard for me to work out exactly what we're trying to do with > "client". It's used for the referrer; anything else? It's the thing SW uses to talk back to the environment the fetch originated from. -- http://annevankesteren.nl/
Received on Tuesday, 29 July 2014 09:32:26 UTC