Use SetUserText() in OmniboxViewViews emphasis tests to ensure system coherence.

chrome/browser/ui/views/omnibox/omnibox_view_views.h

Index: chrome/browser/ui/views/omnibox/omnibox_view_views.h
diff --git a/chrome/browser/ui/views/omnibox/omnibox_view_views.h b/chrome/browser/ui/views/omnibox/omnibox_view_views.h
index 5184a7da22ab72e1011fec4b44ab32da4456626f..cff0a52819ff9c27882cd2f6f6fd38ccd349cea3 100644
--- a/chrome/browser/ui/views/omnibox/omnibox_view_views.h
+++ b/chrome/browser/ui/views/omnibox/omnibox_view_views.h
@@ -85,6 +85,7 @@ class OmniboxViewViews
   // OmniboxView:
   void Update() override;
   base::string16 GetText() const override;
+  using OmniboxView::SetUserText;

[elawrence, 2017/03/04 18:41:48]

I must plead ignorance to what this using declaration does.

[Peter Kasting, 2017/03/06 21:18:03]

It exposes the base class methods that are not overridden in this class to name
lookup.  In this case, it lets me call the one-arg SetUserText() in the base
class without doing:

  static_cast<OmniboxView*>(ptr)->SetUserText(...);

Or:

  ptr->OmniboxView::SetUserText(...);

...both of which feel more ugly, and force each caller that wants this to do it.

   void SetUserText(const base::string16& text,
                    bool update_popup) override;
   void EnterKeywordModeForDefaultSearchProvider() override;