- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 15 Jan 2010 14:41:40 +0100
- To: Maciej Stachowiak <mjs@apple.com>
- CC: Leonard Rosenthol <lrosenth@adobe.com>, Adam Barth <w3c@adambarth.com>, Ian Hickson <ian@hixie.ch>, "public-html@w3.org WG" <public-html@w3.org>
Maciej Stachowiak wrote: > On Jan 13, 2010, at 12:30 PM, Leonard Rosenthol wrote: > >> Adobe is certainly committed to working with this committee and others >> to develop the necessary specifications, APIs, etc. that would ensure >> that our plugins would operate correctly with @sandbox. >> >> Maciej - your company is also a vendor of popular plugins (eg. >> Quicktime). Ian, yours is now doing them for 3D and others. Are you >> two also willing to participate? If so, that would cover about 90+% >> of the major plugins in use today. > > I can see how it may be useful to allow sandboxed content to embed media > via QuickTime. > >> So what is the correct course of action to see that move forward? > > One good way is to make a proposal on the plugin-futures list. That is > the venue for discussing and extending the "NPAPI" plugin API, which is > used by all browsers other than IE. IE uses ActiveX instead, presumably > the right way to request extensions to ActiveX is to contact Microsoft. > > Regards, > Maciej As there are at least two different plugin APIs, we probably shouldn't couple the specification of "allow-plugins" to concrete progress in updating these APIs. What's needed on HTML5 side is a precise definition of what that keyword would mean. If in the short term it'll be a no-op because no plugin API supports it that shouldn't be a problem. Best regards, Julian
Received on Friday, 15 January 2010 13:42:20 UTC