On Wed, Mar 11, 2009 at 2:07 PM, Brett Wilson <[email protected]> wrote:
> Do you mean when you click on the menu, blocking the browser until the > renderer responds with whether the menus can be enabled? I would be > opposed to that. > Right, that would be bad for us. But for most users of WebCore, such a thing would be fine (since, without process separation, there's a million ways for the renderer to hose the browser, and this is the least of their concerns). > State changes won't fix the problem either. There is no way in the > browser to know about the current state of the renderer without one or > the other one blocking. State change notifications don't address this > problem. I fail to see your problem. The renderer sends notifications about its state, and the browser uses the last (cached) value to present its menus as correctly as it can to the user. Avi --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
