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

Re: Isolated Script API

From: Elliott Sprehn <esprehn@chromium.org>
Date: Fri, 14 Aug 2015 17:23:05 -0700
Message-ID: <CAO9Q3i+GP-O8e9At0ncKYuD-fqwF+HavPrhFok3OTJOM+ZxJjg@mail.gmail.com>
To: Chris Lilley <chris@w3.org>
Cc: Ian Kilpatrick <ikilpatrick@chromium.org>, "public-houdini@w3.org" <public-houdini@w3.org>
On Fri, Aug 14, 2015 at 5:31 AM, Chris Lilley <chris@w3.org> wrote:

> Hello Ian,
>
> Tuesday, August 11, 2015, 2:56:12 AM, you wrote:
>
> > 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.
>
> I believe we will, yes. It seems safer and is probably more
> performant, even though the main rendering thread should not be
> blocked which removes the major perf worry.
>

This is not intended to be off main thread, just in a different context. In
the same way that two iframes have separate scripting contexts but are in
the same thread.

Using an isolated context means the script can run directly inside
.getBoundingClientRect() in the layout process of the engine, places where
running script is not generally safe.

- E
Received on Saturday, 15 August 2015 00:24:17 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 15 August 2015 00:24:18 UTC