tonikitoo at gmail.com
Mon Oct 17 07:03:59 PDT 2011
As far as I can tell, the whole DOM is traversed every time a movement is
going to happen. I've discussed with Yael briefly on the WebKit summit about
some cache mechanisms, but we could not get a nice heuristic to invalidate
Have you profiled it?
On Mon, Oct 17, 2011 at 7:29 AM, Sanjeet Pratap Singh <
sanjeetpratapsingh at gmail.com> wrote:
> Hi All,
> I am a beginner to WebKit, looking into "*Spatial-Navigation*" feature of
> I am looking further for some optimisations in the same.
> I find there "*findFocusCandidateInContainer() "* in which we start
> from first child of "container" and iterate until the we get the focus
> My question is,"Are we checking the whole DOM tree to find the closest node
> or we have a small area(container) accordingly?"
> What does the function*
> "container=scrollableEnclosingBoxOrParentFrameForNodeInDirection()"* do?
> Waiting for the reply.
> Thanks & Regards,
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev