W3C home > Mailing lists > Public > public-html@w3.org > January 2010

Re: What defines a "plugin"? WRT sandboxing?

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 27 Jan 2010 18:06:02 +0100
Message-ID: <4B60727A.2050807@gmx.de>
To: Adam Barth <w3c@adambarth.com>
CC: Leonard Rosenthol <lrosenth@adobe.com>, Maciej Stachowiak <mjs@apple.com>, "public-html@w3.org" <public-html@w3.org>
Adam Barth wrote:
> On Tue, Jan 26, 2010 at 9:10 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
>> Adam Barth wrote:
>>> The long term solution is to let plugins participate in the sandbox
>>> security model and then add an allow-plugins directive that re-enables
>>> them, which is where this thread started N thousand words ago.
>> Indeed.
>>
>> Can we please try to make process here?
> 
> Yes, that would be much better than going in circles here.  :)
> 
> There was another fellow from Adobe who was interested in helping with
> specifying the API.  Have you synched up with him?

Leonard, are you subscribed to plugin-futures yet?

>> I have started a Wiki page at <https://wiki.mozilla.org/Plugins:SandboxedPlugins>,
> 
> That looks to be mostly requirements.  I think we need someone to step
> up and propose an API.  I can help, but it will take me a bit to get
> up to speed on NPAPI.  We should continue this discussion on
> plugin-futures.
> ...

I'd like to nail down what the requirements are first; this is, as 
Maciej pointed out, necessary for the discussion how to specify the 
allow-plugins attribute.

Mapping the requirements to an API proposal doesn't appear to be hard...

>> and I have also pointed
>> out that HTML5 currently doesn't have a solid definition of "plugin" (see
>> <http://lists.w3.org/Archives/Public/public-html/2010Jan/1275.html>) --
>> should I open a BugZilla issue for that?
> 
> That can't hurt.  :)

I've done that in the meantime.

Best regards, Julian
Received on Wednesday, 27 January 2010 17:06:44 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:13 UTC