  
  @end
 diff --git a/content/browser/renderer_host/render_widget_host_view_mac.mm b/content/browser/renderer_host/render_widget_host_view_mac.mm
-index 9ce93d256d4f1c3cdaaa277f7d09987c621a0731..d4bed59d1ea0ec6382faabd56ea4dc0659a605f6 100644
+index b7f8bad5ef1a10c5d2e9ac4d83f87e069dbd179a..615023a1338aa05cc2ba2a60ae5fe218d7c13180 100644
 --- a/content/browser/renderer_host/render_widget_host_view_mac.mm
 +++ b/content/browser/renderer_host/render_widget_host_view_mac.mm
 @@ -139,6 +139,12 @@ RenderWidgetHostView* GetRenderWidgetHostViewToUse(

 
   if ([theEvent type] == NSFlagsChanged) {
     // Ignore NSFlagsChanged events from the NumLock and Fn keys as
@@ -2422,14 +2441,18 @@ void RenderWidgetHostViewMac::OnDisplayMetricsChanged(
   // do so. For this reason, for now, we accept this non-ideal way of fixing the
   // point offset manually from the view bounds. This should be revisited when
   // fixing issues in TextInputClientMac (https://crbug.com/643233).

   // If we return |NO| from this function, cocoa will send the key event to
   // the menu and only if the menu does not process the event to |keyDown:|. We
   // want to send the event to a renderer _before_ sending it to the menu, so
@@ -2015,6 +2031,7 @@ void RenderWidgetHostViewMac::OnDisplayMetricsChanged(
     DCHECK(![[NSApp mainMenu] performKeyEquivalent:theEvent]);
     return NO;
   }
