W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2009

[whatwg] Application defined "locks"

From: Darin Fisher <darin@chromium.org>
Date: Wed, 9 Sep 2009 21:57:03 -0700
Message-ID: <bd8f24d20909092157t58e665a3o3024da27a4ca7dff@mail.gmail.com>
On Wed, Sep 9, 2009 at 9:43 PM, Robert O'Callahan <robert at ocallahan.org>wrote:

> On Thu, Sep 10, 2009 at 4:37 PM, Darin Fisher <darin at chromium.org> wrote:
>
>>  Imagine if you script a plugin inside the transaction, and before
>> returning, the plugin scripts another window,
>>
>
> I'm curious, how common is that anyway? Can we just tell plugins not to do
> that, and abort any plugin that tries?
>
>
I don't know.  Are you saying that a plugin should not be able to invoke a
function that may trigger showModalDialog?  The code that calls
showModalDialog may be far removed / unrelated to the plugin script.  It may
just be an unfortunate side effect of invoking a method on a DOM window.

-Darin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090909/6377a47a/attachment-0001.htm>
Received on Wednesday, 9 September 2009 21:57:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:52 UTC