The context menu does some kind of hit test on the renderer and gets back info about what's under the mouse. I think the IPC message that comes back from the renderer knows whether cut/copy/paste should be enabled. I guess that's evidence that round-tripping through the renderer to get this state might not be that bad for the page menu.
Adam On Mon, Mar 9, 2009 at 1:14 PM, Avi Drissman <[email protected]> wrote: > Oh, that's curious. Where does the context menu come from? And how does it > know? > > Avi > > On Mon, Mar 9, 2009 at 2:04 PM, Adam Barth <[email protected]> wrote: >> >> Thanks. I always use our context menu, which seems to be smarter >> about disabling cut/copy/paste. >> >> Adam >> >> >> On Mon, Mar 9, 2009 at 12:00 PM, Evan Martin <[email protected]> wrote: >> > On Mon, Mar 9, 2009 at 11:43 AM, Adam Barth <[email protected]> wrote: >> >> On Mon, Mar 9, 2009 at 9:53 AM, Avi Drissman <[email protected]> wrote: >> >>> For those unfamiliar, the copy/paste menu items are always enabled, >> >>> and send >> >>> a message to TabContents. >> >> >> >> Do you have an example of how to reproduce this issue? On Windows, >> >> the Cut/Copy/Paste menu items are often disabled when they won't work. >> > >> > 1) Change your sound scheme to "Windows default". >> > 2) Make sure no text is selected in Chrome. >> > 3) Page menu -> copy. Beep! Also beeps if you hit ctl-c while typing. >> > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
