- From: Adam Barth <w3c@adambarth.com>
- Date: Mon, 18 Jan 2010 10:33:51 -0800
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Maciej Stachowiak <mjs@apple.com>, Leonard Rosenthol <lrosenth@adobe.com>, Ian Hickson <ian@hixie.ch>, "public-html@w3.org WG" <public-html@w3.org>
On Mon, Jan 18, 2010 at 10:20 AM, Julian Reschke <julian.reschke@gmx.de> wrote: > Adam Barth wrote: >> We might want to support something like Content-Security-Policies in >> the future, so an extensible set of flags seems like a good idea. I'm >> not sure we should design the API on this list, but you could imagine >> wanting to know which flags the plug-in supports instead of just >> having a single "supports sandboxing" bit. > > Would a whitespace-separated list of tokens work? (similar to what > iframe/@sandbox takes) I'm not overly familiar with the style of NPAPI. That seems reasonable. Some sort of bit field might also be reasonable. The plugin-futures folks are the experts here. Adam
Received on Monday, 18 January 2010 18:34:43 UTC