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

What defines a "plugin"? WRT sandboxing?

From: Leonard Rosenthol <lrosenth@adobe.com>
Date: Sun, 24 Jan 2010 05:44:31 -0800
To: "public-html@w3.org" <public-html@w3.org>
Message-ID: <D23D6B9E57D654429A9AB6918CACEAA97CA3417160@NAMBX02.corp.adobe.com>
When defining and implementing sandboxing, is the requirement to disable plugins restricted ONLY to actual technologies implemented by plugins to the browser/UA _OR_ does it really mean content not in a format documented by the HTML5 spec.

For example, Safari (on the Mac) knows how to natively view PDF documents.  If Safari encounters an HTML document with a reference to an embedded PDF (<object> or <embed>) it will currently render that document through its own technology, whereas other browsers will use available plugins to do so.  When that same HTML is now served as sandbox, then clearly the other browsers will stop viewing PDF - but should Safari?

OR consider Adobe AIR which (through WebKit) can act as an HTML5 UA and incorporates native support for Flash.  Does it have to disable Flash, since it isn't using sandbox?

Looking forward to the discussion...

Leonard
Received on Sunday, 24 January 2010 13:45:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:00 GMT