Implement the Instant extended API startMargin, endMargin, and rtl properties and the onmarginchang…

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

Index: chrome/browser/ui/views/omnibox/omnibox_view_views.cc
diff --git a/chrome/browser/ui/views/omnibox/omnibox_view_views.cc b/chrome/browser/ui/views/omnibox/omnibox_view_views.cc
index 76c7453d52281e7fb2c4f4c2b2c1d68aca638a8b..aea2d9fc1e936bca62cfbe75343c582b8abf45b1 100644
--- a/chrome/browser/ui/views/omnibox/omnibox_view_views.cc
+++ b/chrome/browser/ui/views/omnibox/omnibox_view_views.cc
@@ -441,6 +441,12 @@ std::string OmniboxViewViews::GetClassName() const {
 void OmniboxViewViews::OnBoundsChanged(const gfx::Rect& previous_bounds) {
   if (popup_view_->IsOpen())
     popup_view_->UpdatePopupAppearance();
+
+  // Pass the location bar's bounds to the edit model because the OmniboxView
+  // does not fill the entire box when gray text is showing. We also pass the
+  // parent view's bounds so that the end margin can be calculated.

[sreeram, 2012/11/29 19:22:49]

What does "gray text" have to do with this? I thought the page needed the
omnibox bounds so that it could size its suggestions list accordingly.

[melevin, 2012/11/30 23:37:09]

Yes, that's what we need it for. But we can't use the dimensions of the
OmniboxView for that. When gray text is showing that view does not fill the
entire location bar.

+  model()->OnOmniboxBoundsChanged(location_bar_view_->GetBoundsInScreen(),
+      location_bar_view_->parent()->GetBoundsInScreen());
 }
 
 ////////////////////////////////////////////////////////////////////////////////