Updates:
Status: Available
Owner: ---
Labels: -Mstone-5 Mstone-X
Comment #5 on issue 26519 by [email protected]: Need to re-architect
nestableTasksAllowed in MessageLoops
http://code.google.com/p/chromium/issues/detail?id=26519
MessageLoop::PostNonNestableTask gives the caller the ability to control
whether or not
their task will run from a nested loop. That seems to address the primary
ask of this
bug. How is that insufficient?
What's the difference between ModalState and EventTrackingState? What is
the pile of
workaround code on the Mac side that you refer to?
(This does not seem like a M5 blocker to me.)
--
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
