Make <a ping> work for context menus.

chrome/browser/renderer_context_menu/render_view_context_menu.cc

Index: chrome/browser/renderer_context_menu/render_view_context_menu.cc
diff --git a/chrome/browser/renderer_context_menu/render_view_context_menu.cc b/chrome/browser/renderer_context_menu/render_view_context_menu.cc
index 672fde34428a8d52d454ef7d0f498d0586c029df..02f73b7751f588b00d2181d6d56009dcc6b2010b 100644
--- a/chrome/browser/renderer_context_menu/render_view_context_menu.cc
+++ b/chrome/browser/renderer_context_menu/render_view_context_menu.cc
@@ -1937,6 +1937,9 @@ void RenderViewContextMenu::OpenURL(
   content::Referrer referrer(referring_url.GetAsReferrer(),
       params_.referrer_policy);
 
+  if (params_.link_url == url && disposition != OFF_THE_RECORD)
+    params_.custom_context.link_followed = url;

[Nate Chapin, 2014/07/14 19:01:46]

The meat of the change. We set link_followed in certain cases so that the
HTMLAnchorElement in the renderer process gets a chance to send pings. If
link_followed is left invalid, no pings will be sent.

The rule here is:
* A protocol handler might translate the url, or this function could be called
for an image/video context menu (which set a different parameter than link_url).
So, don't give the renderer a chance to ping if the URL wasn't exactly the
link_url that the renderer process provided.
* If this link is being opened off the record, we suppress referrers, so
suppress pings as well. This seems to match the intent of the user in severing
any connections between the referring page and the destination page.

+
   WebContents* new_contents = source_web_contents_->OpenURL(OpenURLParams(
       url, referrer, disposition, transition, false));
   if (!new_contents)