Don't make :hover sticky on tap on sites that set a mobile viewport set

Source/core/rendering/HitTestRequest.h

Index: Source/core/rendering/HitTestRequest.h
diff --git a/Source/core/rendering/HitTestRequest.h b/Source/core/rendering/HitTestRequest.h
index 272c0a20222eae54294974dbc9b874fcbcb852bf..f53b1e85381ad2b984efbb8cadd7c5dfe1d9e406 100644
--- a/Source/core/rendering/HitTestRequest.h
+++ b/Source/core/rendering/HitTestRequest.h
@@ -38,6 +38,7 @@ public:
         AllowChildFrameContent = 1 << 8,
         ChildFrameHitTest = 1 << 9,
         IgnorePointerEventsNone = 1 << 10,
+        Hover = 1 << 11,

[Rick Byers, 2014/11/17 22:00:10]

It's a little confusing to explicitly opt-in to hover, when Active, Move and
Release already normally imply Hover.

Perhaps instead we should invert this by adding a new 'Leave' flag which (when
applied on conjunction with Release) forces hover to be cleared.

I know the existing code isn't well commented here, but please add a comment
describing the meaning of this new bit since it's rather subtle.

     };
 
     typedef unsigned HitTestRequestType;
@@ -57,6 +58,7 @@ public:
     bool allowsChildFrameContent() const { return m_requestType & AllowChildFrameContent; }
     bool isChildFrameHitTest() const { return m_requestType & ChildFrameHitTest; }
     bool ignorePointerEventsNone() const { return m_requestType & IgnorePointerEventsNone; }
+    bool hover() const { return m_requestType & Hover; }
 
     // Convenience functions
     bool touchMove() const { return move() && touchEvent(); }