- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 03 Jun 2010 18:29:13 +0200
- To: Artur Adib <arturadib@gmail.com>
- CC: public-html@w3.org, Leonard Rosenthol <lrosenth@adobe.com>, Adam Barth <w3c@adambarth.com>, Ian Hickson <ian@hixie.ch>
On 03.06.2010 17:55, Artur Adib wrote: > ... > Any thoughts? > ... Pointers: there's a Mozilla mailing list (see <https://mail.mozilla.org/listinfo/plugin-futures>) and a Wiki where NSAPI extensions are discussed; I started discussion of this a while ago at https://wiki.mozilla.org/Plugins:SandboxedPlugins This needs review and feedback. A more general issue is that HTML5 doesn't really defined what a plugin is *precisely*. I have opened two bugs with respect to this: http://www.w3.org/Bugs/Public/show_bug.cgi?id=8828 http://www.w3.org/Bugs/Public/show_bug.cgi?id=9221 but wasn't successful in getting the spec to the point where it's precise enough to argue about the whole issue. My proposal would be not to make any requirements on plugins *unless* we have a clear understanding what a plugin is. With respect to sandboxing, this should be rephrased to define the actual restrictions (navigation, scripting, ...), and then have a plugin API extension that allows to pass this information down to the plugin. Best regards, Julian
Received on Thursday, 3 June 2010 16:29:57 UTC