Disable Views fuzzing with --disable-views-rect-based-targeting.

ui/views/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.
 
 #define _USE_MATH_DEFINES // For VC++ to get M_PI. This has to be first.
 
 #include "ui/views/view.h"
 
 #include <algorithm>
 #include <cmath>
@@ skipping 24 matching lines @@
 #include "ui/gfx/transform.h"
 #include "ui/native_theme/native_theme.h"
 #include "ui/views/accessibility/native_view_accessibility.h"
 #include "ui/views/background.h"
 #include "ui/views/border.h"
 #include "ui/views/context_menu_controller.h"
 #include "ui/views/drag_controller.h"
 #include "ui/views/layout/layout_manager.h"
 #include "ui/views/rect_based_targeting_utils.h"
 #include "ui/views/views_delegate.h"
+#include "ui/views/views_switches.h"
 #include "ui/views/widget/native_widget_private.h"
 #include "ui/views/widget/root_view.h"
 #include "ui/views/widget/tooltip_manager.h"
 #include "ui/views/widget/widget.h"
 
 #if defined(USE_AURA)
 #include "ui/base/cursor/cursor.h"
 #endif
 
 #if defined(OS_WIN)
@@ skipping 35 matching lines @@
 
 namespace internal {
 
 // This event handler receives events in the post-target phase and takes care of
 // the following:
 //   - Generates context menu, or initiates drag-and-drop, from gesture events.
 class PostEventDispatchHandler : public ui::EventHandler {
  public:
   explicit PostEventDispatchHandler(View* owner)
       : owner_(owner),
-        touch_dnd_enabled_(switches::IsTouchDragDropEnabled()) {
+        touch_dnd_enabled_(::switches::IsTouchDragDropEnabled()) {
   }
   virtual ~PostEventDispatchHandler() {}
 
  private:
   // Overridden from ui::EventHandler:
   virtual void OnGestureEvent(ui::GestureEvent* event) OVERRIDE {
     DCHECK_EQ(ui::EP_POSTTARGET, event->phase());
     if (event->handled())
       return;
 
@@ skipping 831 matching lines @@
   return gfx::kNullCursor;
 #endif
 }
 
 bool View::HitTestPoint(const gfx::Point& point) const {
   return HitTestRect(gfx::Rect(point, gfx::Size(1, 1)));
 }
 
 bool View::HitTestRect(const gfx::Rect& rect) const {
   if (GetLocalBounds().Intersects(rect)) {
-    if (HasHitTestMask()) {
+    if (views::switches::IsRectBasedTargetingEnabled() && HasHitTestMask()) {

[sadrul, 2014/01/23 00:40:42]

Does this break hit-testing along the slanted edges of the tabs?

[msw, 2014/01/23 00:54:32]

Hmm, yeah. Adjacent tabs obscure the right half of the (x) button's hit test
rect. So --disable-views-rect-based-targeting makes only the left half
responsive to hover/click, even with normal sized system fonts. That's not good,
but still better for users that can't click the (x) button at all. Shrikant's
layout/mask will be better for the long term, but this is still a potentially
viable way to help M-32 users suffering from Issue 332334. I'm open to
alternate/additional fix ideas.

       gfx::Path mask;
       HitTestSource source = HIT_TEST_SOURCE_MOUSE;
       if (!views::UsePointBasedTargeting(rect))
         source = HIT_TEST_SOURCE_TOUCH;
       GetHitTestMask(source, &mask);
 #if defined(USE_AURA)
       // TODO: should we use this every where?
       SkRegion clip_region;
       clip_region.setRect(0, 0, width(), height());
       SkRegion mask_region;
@@ skipping 1424 matching lines @@
   // Message the RootView to do the drag and drop. That way if we're removed
   // the RootView can detect it and avoid calling us back.
   gfx::Point widget_location(event.location());
   ConvertPointToWidget(this, &widget_location);
   widget->RunShellDrag(this, data, widget_location, drag_operations, source);
   // WARNING: we may have been deleted.
   return true;
 }
 
 }  // namespace views