W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2011

[Bug 13267] sandboxing implication for plugins should be rephrased

From: <bugzilla@jessica.w3.org>
Date: Fri, 15 Jul 2011 19:04:47 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qhngt-0000V5-0U@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13267

Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Simetrical+w3cbug@gmail.com

--- Comment #1 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-07-15 19:04:46 UTC ---
Specifically, it would make the most sense to remove "plugins are disabled",
and add a sentence saying that the UA has to only allow plugins to run if it
knows they'll meet these requirements.  E.g., NPAPI might be extended to have
flags to signal this sort of thing, or maybe the browsers authors control the
plugin themselves (like the Chrome PDF viewer).

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 15 July 2011 19:04:48 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:13 UTC