DevTools: [CodeMirror] show native copy/paste/cut items in editor context menu

DevTools: [CodeMirror] show native copy/paste/cut items in editor context menu

Currently, if you select some text in text editor and then do a right-click
inside selection, the just-summoned context menu won't have a copy/paste/cut
items, as well as other native items natural for text area context menu.

This happens due to the way CodeMirror handles contextmenu event. It
focuses a small text area during the contextmenu bubbling phase, so the
upcoming ContextMenu gets populated with appropriate items. Unfortunately,
codemirror does all this textarea mess *after* firing its own "contextmenu"
event, and as we create menu in the listener, it doesn't have correct active
element.

This patch goes back to listening contextmenu event on element, which due to
bubbling nature happens after textarea was focused.

R=vsevik

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=175286

[lushnikov, 2014-06-02 13:04:48]

ptal!

[vsevik, 2014-06-02 13:36:48]

lgtm

[commit-bot: I haz the power, 2014-06-02 13:37:02]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/lushnikov@chromium.org/306023015/1

[commit-bot: I haz the power, 2014-06-02 14:52:15]

Change committed as 175286

[pfeldman, 2014-06-02 15:15:10]

Should we get a list of manual tests for the codemirror rolls? Sort of a
checklist. It seems like this one is hard to test automatically.

[lushnikov, 2014-06-02 19:19:23]

On 2014/06/02 15:15:10, pfeldman_ooo wrote:
> Should we get a list of manual tests for the codemirror rolls? Sort of a
> checklist. It seems like this one is hard to test automatically.

It wasn't a roll that regressed this - that was me..

But anyhow, I already do manual testing for every CM roll. So far it doesn't
regularly regress functionality, does it?

[lushnikov, 2014-06-02 19:20:49]

The CL that regressed this: https://codereview.chromium.org/247013004/

[pfeldman, 2014-06-03 05:53:46]

> But anyhow, I already do manual testing for every CM roll. So far it doesn't
> regularly regress functionality, does it?

So far, it worked perfectly, and that is why we should capture the scenarios you
check  upon every roll. That way you are not the only one who can make a quality
roll + you don't forget all the things you check. A simple text file with a list
of things to check before roll lands is more than enough.