Changeset 112148 in webkit
- Timestamp:
- Mar 26, 2012 2:43:55 PM (12 years ago)
- Location:
- trunk/Source/WebCore
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/Source/WebCore/ChangeLog
r112144 r112148 1 2012-03-26 Anders Carlsson <andersca@apple.com> 2 3 Find in page overlay and bouncy are not always positioned correctly 4 https://bugs.webkit.org/show_bug.cgi?id=82247 5 <rdar://problem/10866139> 6 7 Reviewed by Sam Weinig. 8 9 In WebCore, a lot of code depends on scroll position updates to happen synchronously, so 10 update the frame view scroll position before asking the scrolling thread to scroll. 11 12 * page/scrolling/ScrollingCoordinator.cpp: 13 (WebCore::ScrollingCoordinator::requestScrollPositionUpdate): 14 1 15 2012-03-26 Nate Chapin <japhet@chromium.org> 2 16 -
trunk/Source/WebCore/page/scrolling/ScrollingCoordinator.cpp
r112142 r112148 229 229 230 230 #if ENABLE(THREADED_SCROLLING) 231 // Update the main frame scroll position locally before asking the scrolling thread to scroll, 232 // since FrameView expects scroll position updates to happen synchronously. 233 updateMainFrameScrollPosition(scrollPosition); 234 231 235 ScrollingThread::dispatch(bind(&ScrollingTree::setMainFrameScrollPosition, m_scrollingTree.get(), scrollPosition)); 232 236 return true;
Note: See TracChangeset
for help on using the changeset viewer.