> Where qtwebkit_webframe_scrollOverflow needs to each and every time do an > elementForPoint() to find the element, etc.
Could some kind of caching help here? Granted, there will be extra cache bookkeeping, though. > QWebScrollController* scrollControllerForPoint(const Qpoint&); > > The QWebScrollController itself would basically provide the position, scroll > range and visible size of the "thing" being scrolled, would allow the the > position to be set, and would emit signals when range/position change. It > would then internally handle whether it's scrolling a frame or an element > with overflow:scroll/auto (and would keep a pointer to it around so that it > doesn't need to figure it out for every move event). > > Thoughts? Is there a better way to do it today that I'm missing? Makes sense. I'd opt for a simpler "QWebScroller" class name. Regards, Ariya _______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
