Componentize FIND_IN_PAGE_* strings

chrome/browser/ui/cocoa/find_bar/find_bar_text_field_cell.mm

 // Copyright (c) 2009 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #import "chrome/browser/ui/cocoa/find_bar/find_bar_text_field_cell.h"
 
 #include "base/logging.h"
 #include "base/strings/string_number_conversions.h"
 #include "base/strings/string_util.h"
 #include "base/strings/sys_string_conversions.h"
-#include "chrome/grit/generated_resources.h"
+#include "components/strings/grit/components_strings.h"

[sdefresne, 2016/02/09 11:53:01]

nit: it seems more common to include grit/components_strings.h in chrome/

[droger, 2016/02/09 12:14:30]

I'm pretty sure using the full path is the right way, and there is a bug to
convert all includes to use the full path:
https://code.google.com/p/chromium/issues/detail?id=401588

[sdefresne, 2016/02/09 12:41:36]

Thank you for the pointer. LGTM without comments then!

 #include "ui/base/l10n/l10n_util.h"
 
 namespace {
 
 // How far to offset the keyword token into the field.
 const NSInteger kResultsXOffset = 3;
 
 // How much width (beyond text) to add to the keyword token on each
 // side.
 const NSInteger kResultsTokenInset = 3;
@@ skipping 85 matching lines @@
   [resultsString_.get() drawInRect:infoFrame];
 }
 
 - (void)drawInteriorWithFrame:(NSRect)cellFrame inView:(NSView*)controlView {
   if (resultsString_)
     [self drawResultsWithFrame:cellFrame inView:controlView];
   [super drawInteriorWithFrame:cellFrame inView:controlView];
 }
 
 @end