W3C home > Mailing lists > Public > public-webappsec@w3.org > April 2015

Re: Privileged context features and JavaScript

From: Elliott Sprehn <esprehn@chromium.org>
Date: Fri, 17 Apr 2015 00:38:08 -0700
Message-ID: <CAO9Q3i+u5BQecgXeO240ix0SBUT8JzaJAZHbwaV4HTCYd7YWZw@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Anne van Kesteren <annevk@annevk.nl>, Mike West <mkwst@google.com>, public-webappsec@w3.org, public-webapps <public-webapps@w3.org>, public-script-coord <public-script-coord@w3.org>
It's preferable not to do that for us because you can then create a static
heap snapshot at compile time and memcpy to start JS contexts faster.
On Apr 17, 2015 12:03 AM, "Boris Zbarsky" <bzbarsky@mit.edu> wrote:

> On 4/17/15 2:52 AM, Boris Zbarsky wrote:
>> If that preference is toggled, we in fact remove the API entirely, so
>> that "'geolocation' in navigator" tests false.
> Oh, I meant to mention: this is more web-compatible than having the API
> entrypoints throw, because it can be object-detected.  Of course we could
> have made the API entrypoints just always reject the request instead, I
> guess; removing the API altogether was somewhat simpler to do.
> -Boris
Received on Friday, 17 April 2015 07:38:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:48 UTC