W3C home > Mailing lists > Public > public-houdini@w3.org > August 2015

Isolated Script API

From: Ian Kilpatrick <ikilpatrick@chromium.org>
Date: Tue, 11 Aug 2015 10:56:12 +1000
Message-ID: <CAJL3UpR==CVw4BKubyVh7ttMiHCPBgomb8zgoCZj-no3UK4Haw@mail.gmail.com>
To: public-houdini@w3.org
Hi all,

For the Houdini APIs which extend the rendering pipeline, we believe that
we'll need an isolated execution environment for these APIs to be exposed
in.

For example, the CSS Paint API (
https://drafts.css-houdini.org/css-paint-api/) allows authors to hook into
the paint phase of rendering. We don't think that it would be good for the
web platform to allow full DOM, network, etc access during paint, because:
 - Allows potential performance foot-guns.
 - Doesn't lead to a rational platform.
 - Doesn't allow performance optimizations on behalf of UAs.

I've written down some initial thoughts here:
http://bfgeek.com/css-houdini-drafts/css-script-api/Overview.html

In this spec I haven't written down where all the other APIs would be
exposed so use your imagination.

As always, let me know of your thoughts!

Thanks,
Ian
Received on Tuesday, 11 August 2015 00:56:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 11 August 2015 00:56:42 UTC