Bug 39217

It would be useful if scrollOverflow and scrollRecursively methods of EventHandler had an optional parameter to be the starting point of a scroll action. For example, currently, EventHandler::scrollOverflow starts a scrolling off of either a 'focusedNode' of a m_'mousePressNode' (see below): bool EventHandler::scrollOverflow(...) { Node* node = m_frame->document()->focusedNode(); if (!node) node = m_mousePressNode.get(); (...) but it would be useful, for Spatial Navigation purposes, that we could pass a Node for the scrolling to start from. scenario (see illustration below): 1) a focused node called "focused", an overflow div (with a clipped overflow focusable node called "offscreen"); 2) user presses key down. 3) Focus should move to "offscreen", but since it is clipped overflow, spatial navigation will scroll-in-direction until it gets visible. -------------------------------- ********* *focused* ********* vertically overflowed div ******************** * * * * * * * * * * * * ******************** . . . *offscreen* . -------------------- -------------------------------- In order to scroll the overflowed div, it is needed to pass to EventHandler::scrollOverflow a starting Node, so it will scroll what I send it to scroll. Otherwise its assumptions to get the node from where to start scrolling from wont help Spatial Navigation. patch coming ...