Fixes vertical misalignment of IME autocompletion.

chrome/browser/ui/views/location_bar/location_bar_view.cc

Index: chrome/browser/ui/views/location_bar/location_bar_view.cc
diff --git a/chrome/browser/ui/views/location_bar/location_bar_view.cc b/chrome/browser/ui/views/location_bar/location_bar_view.cc
index 72a84ce3a9d8985274c0a5ce3c84e979787e033a..3cd60393edcfaadf75a18fee2ccf83ddb73c24ed 100644
--- a/chrome/browser/ui/views/location_bar/location_bar_view.cc
+++ b/chrome/browser/ui/views/location_bar/location_bar_view.cc
@@ -880,8 +880,11 @@ void LocationBarView::Layout() {
     else if (location_needed_width + width > entry_width)
       x = entry_width - width;
     location_bounds.set_width(x);
+    const int baseline_diff = location_entry_view_->GetBaseline() -

[Peter Kasting, 2013/08/09 19:00:48]

Instead of doing this here, shouldn't we be doing it where the view is created
and we already give it a y offset?

Is the y offset we set there wrong due to font list differences?

[Yuki, 2013/08/12 06:30:14]

That's right.  I've moved the code to the initialization part.

And yes, because views::Label currently takes only the first font in the font
list while views::Textfield takes the whole font list, the baselines mismatch.

I'm now fixing views::Label and related code, but it will take time.  After I'll
fix it, we'll be able to pass the same FontList to
ime_inline_autocomplete_view_.

+                              ime_inline_autocomplete_view_->GetBaseline();
     ime_inline_autocomplete_view_->SetBounds(
-        location_bounds.right(), location_bounds.y(),
+        location_bounds.right(),
+        location_bounds.y() + baseline_diff,
         std::min(width, entry_width),
         ime_inline_autocomplete_view_->GetPreferredSize().height());
   }