Send mouse exited event after mouse release outside view.

ui/views/widget/root_view.cc

 // Copyright (c) 2012 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.
 
 #include "ui/views/widget/root_view.h"
 
 #include <algorithm>
 
 #include "base/logging.h"
 #include "base/macros.h"
@@ skipping 34 matching lines @@
                        static_cast<View*>(NULL),
                        static_cast<View*>(NULL)) {
     DCHECK(type == ui::ET_MOUSE_ENTERED ||
            type == ui::ET_MOUSE_EXITED);
     SetType(type);
   }
 
   ~MouseEnterExitEvent() override {}
 };
 
+class GeneratedMouseMoveEvent : public ui::MouseEvent {
+ public:
+  GeneratedMouseMoveEvent(const ui::MouseEvent& event)
+      : ui::MouseEvent(event) {
+    SetType(ui::ET_MOUSE_MOVED);
+  }
+
+  ~GeneratedMouseMoveEvent() override {}
+};
+
 }  // namespace
 
 // This event handler receives events in the pre-target phase and takes care of
 // the following:
 //   - Shows keyboard-triggered context menus.
 class PreEventDispatchHandler : public ui::EventHandler {
  public:
   explicit PreEventDispatchHandler(View* owner)
       : owner_(owner) {
   }
@@ skipping 375 matching lines @@
     ui::MouseEvent mouse_released(event, static_cast<View*>(this),
                                   mouse_pressed_handler_);
     // We allow the view to delete us from the event dispatch callback. As such,
     // configure state such that we're done first, then call View.
     View* mouse_pressed_handler = mouse_pressed_handler_;
     SetMouseHandler(NULL);
     ui::EventDispatchDetails dispatch_details =
         DispatchEvent(mouse_pressed_handler, &mouse_released);
     if (dispatch_details.dispatcher_destroyed)
       return;
+    // We should send generated mouse event, to update hovers after releasing of
+    // mouse capturing.
+    OnMouseMoved(GeneratedMouseMoveEvent(event));

[sadrul, 2016/10/28 16:07:39]

Always sending a mouse-move after a mouse-release doesn't sound like a good idea
to me.

[snake, 2016/10/28 16:21:38]

But we should do this, because View under cursor (which may not
mouse_pressed_handler), don't know that mouse was moved on it before. This is
just post notification about this.

Should I write test on this case?
  The test will be:
   MouseDown on first view.
   Move mouse to second view
   Release mouse on second view.
   Second view should receive mouse exited and mouse moved notifications.

   }
 }
 
 void RootView::OnMouseCaptureLost() {
   // TODO: this likely needs to reset touch handler too.
 
   if (mouse_pressed_handler_ || gesture_handler_) {
     // Synthesize a release event for UpdateCursor.
     if (mouse_pressed_handler_) {
       gfx::Point last_point(last_mouse_event_x_, last_mouse_event_y_);
@@ skipping 297 matching lines @@
 
 #ifndef NDEBUG
   DCHECK(!event_dispatch_target_ || Contains(event_dispatch_target_));
 #endif
 
   return details;
 }
 
 }  // namespace internal
 }  // namespace views