On Fri, Sep 11, 2009 at 2:46 PM, John Tamplin <j...@google.com> wrote:
> On Fri, Sep 11, 2009 at 5:24 PM, Darin Fisher <da...@chromium.org> wrote:
>
>> I think that is a reasonable feature request. It would be nice however if
>> there were some way to know when to restore the old behavior.
>> Unfortunately, Chrome won't know when you are done.
>
>
> I was thinking something like this for my case (substitute appropriate
> method names):
> NPN_SetPluginWarning(false);
> processSocketMessages();
> NPN_SetPluginWarning(true);
>
> and trying to call NPN_SetPluginWarning where you didn't request that
> permission in the manifest would fail.
>
That would work for us too. Seems pretty good -- an easy way for a plugin
to say, "Temporarily disable the hang monitor, because we are going to be
deliberately hung for a little while."
But I don't understand how the manifest would work. I get that you want to
prevent malicious plugins from abusing this, but how does a plugin become
"trusted"? What sort of manifest is this, and where is it (is it in the
plugin, or in Chrome, or somewhere else)?
I'm also fine with the other suggestions, such as making it a bit like
incognito mode, but that seems like potentially quite a lot more work.
P.S. I'll log this as soon as this initial discussion slows down.
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
