Avoid computing navigation data for nodes in the wrong navigation direction

Source/core/page/FocusController.cpp

Index: Source/core/page/FocusController.cpp
diff --git a/Source/core/page/FocusController.cpp b/Source/core/page/FocusController.cpp
index 70c57737cdf428487ab7a45539803ea77e9d5971..dad85c5722bb649e90441c1bedcd0814489d355b 100644
--- a/Source/core/page/FocusController.cpp
+++ b/Source/core/page/FocusController.cpp
@@ -886,6 +886,9 @@ void FocusController::findFocusCandidateInContainer(Node& container, const Layou
         if (candidate.isNull())
             continue;
 
+        if (!isRectInDirection(type, current.rect, candidate.rect))

[fs, 2015/03/18 14:02:11]

Could you perhaps make this the first thing in distanceDataForNode instead? (To
avoid exposing isRectInDirection.) There's not a whole lot of code being run
between here and the suggested placement, so I don't think it makes a big
different "optimization-wise".

[Abhijeet Kandalkar Slow, 2015/03/18 14:26:42]

Done.

+            continue;
+
         candidate.enclosingScrollableBox = &container;
         updateFocusCandidateIfNeeded(type, current, candidate, closest);
     }