Fix a bug in TextInputManager::GetCompositionRangeInfo

content/browser/renderer_host/text_input_manager.cc

Index: content/browser/renderer_host/text_input_manager.cc
diff --git a/content/browser/renderer_host/text_input_manager.cc b/content/browser/renderer_host/text_input_manager.cc
index 6a96396af7686cc5de3898159785027a0511e725..c7c61a2039138065ddd45ac634db14a57e1b2dbe 100644
--- a/content/browser/renderer_host/text_input_manager.cc
+++ b/content/browser/renderer_host/text_input_manager.cc
@@ -77,7 +77,7 @@ TextInputManager::GetCompositionRangeInfo(
   DCHECK(!view || IsRegistered(view));
   if (!view)
     view = active_view_;
-  return active_view_ ? &composition_range_info_map_.at(active_view_) : nullptr;

[EhsanK, 2017/04/10 14:50:29]

Right now we do not actually even use this method for a non-null
|view| (all the calls to the method use the default nullptr value for view).
That being said I am working on moving IME tracking to make use of focused frame
(instead of purely relying on TextInputState) and I guess I will be using this
method on focused view. That said, I can either remove |view| as an argument
here now and maybe add it back later, or just keep it as is for now. WDYT?

[Charlie Reis, 2017/04/10 18:31:21]

Let's go ahead and remove it for now, since it's easy to add back if you need it
later.

[EhsanK, 2017/04/10 18:37:10]

Acknowledged.

+  return view ? &composition_range_info_map_.at(view) : nullptr;
 }
 
 const TextInputManager::TextSelection* TextInputManager::GetTextSelection(