Comment #1 on issue 26519 by [email protected]: Need to re-architect nestableTasksAllowed in MessageLoops http://code.google.com/p/chromium/issues/detail?id=26519
+1. I'm not entirely sure that the implementer of a task can decide whether to handle it, though, because by then the task is already running. The implementer would have to tweak the current message loop to freeze the channel, then arrange to report itself to the front of the channel. The task poster could certainly post with an indicator for which modes the task is runnable. It might be useful to enumerate the special events, here. The things I can think of are creating views, closing views, moving/resizing views, initiating a dialog (alert, print), maybe navigating to a new url, initiating drags. There are probably more, but render_messages_internal.h is melting my brain. Anyhow, I don't think any of those should likely happen when processing a modal event loop or when doing a drag. Navigating to a new url I'm mixed on - sometimes, the modal thing is talking about the current url, after all, but doing that on a tab you can't see seems reasonable. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
