Since the hang dialog comes up in the future after you've shifted your
focus elsewhere, if we did any sort of user interaction at all I'd
rather the plug-in could say "Ask user for permission to disable hang
monitor for this context right now".  The plug-in hits the breakpoint,
calls that function, and on successful return falls into the blocking
mode.  The browser could cache the response so that the user only has
to be asked once per tab (or browser session).


On Fri, Sep 11, 2009 at 3:50 PM, Mike Mammarella <> wrote:
> Perhaps rather than disabling the hang monitor altogether what that
> could do is add an additional option to the warning the first time:
> "don't notify me again." If you click that, then it will disable the
> hang monitor until the plugin is once again responsive and then
> becomes unresponsive again. (Or maybe even until the plugin
> terminates.)
> That avoids the need to have a plugin be trusted in any way, but keeps
> the UI simple unless the plugin knows it wants to display it and get
> debugged. You'd still have to deal with the dialog once but after that
> it would get out of your way.
> --Mike
> On Fri, Sep 11, 2009 at 3:41 PM, Scott Hess <> wrote:
>> Another alternative would be a "ping" type call to say "I'm
>> unresponsive, and I mean it."  Like a watchdog timer.  The plug-in
>> could still effectively be hung, but at least it has to have things
>> together enough to call the watchdog.
>> -scott
>> On Fri, Sep 11, 2009 at 3:37 PM, John Abd-El-Malek <> wrote:
>>> For reference, something similar is done for popups:
>>> void NPN_PushPopupsEnabledState(NPP instance, NPBool enabled);
>>> void NPN_PopPopupsEnabledState(NPP instance);
>>> Perhaps we can do the same thing here:
>>> void NPN_PushPluginHangDetectorState(NPP instance, NPBool enabled);
>>> void NPN_Pop PluginHangDetectorState(NPP instance);
>>> On Fri, Sep 11, 2009 at 2:46 PM, John Tamplin <> wrote:
>>>> On Fri, Sep 11, 2009 at 5:24 PM, Darin Fisher <> 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.
>>>> --
>>>> John A. Tamplin
>>>> Software Engineer (GWT), Google
>>> >
>> >>

Chromium Developers mailing list: 
View archives, change email options, or unsubscribe:

Reply via email to