Changeset 214482 in webkit
- Timestamp:
- Mar 28, 2017 11:29:37 AM (7 years ago)
- Location:
- trunk/Source/WebCore
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/Source/WebCore/ChangeLog
r214481 r214482 1 2017-03-27 Simon Fraser <simon.fraser@apple.com> 2 3 Make sure the non-fast scrolling debug overlay is correctly updated 4 https://bugs.webkit.org/show_bug.cgi?id=170142 5 6 Reviewed by Tim Horton. 7 8 AsyncScrollingCoordinator::frameViewEventTrackingRegionsChanged() is called on a timer 9 from Document code, so the existing DebugPageOverlays::didLayout() call at the end 10 of FrameView::layout() wasn't sufficient to keep the non-fast scrollable region up-to-date 11 on iOS. 12 13 * page/scrolling/AsyncScrollingCoordinator.cpp: 14 (WebCore::AsyncScrollingCoordinator::frameViewEventTrackingRegionsChanged): 15 1 16 2017-03-28 Antoine Quint <graouts@apple.com> 2 17 -
trunk/Source/WebCore/page/scrolling/AsyncScrollingCoordinator.cpp
r212559 r214482 29 29 #include "AsyncScrollingCoordinator.h" 30 30 31 #include "DebugPageOverlays.h" 31 32 #include "Document.h" 32 33 #include "EditorClient.h" … … 197 198 } 198 199 199 void AsyncScrollingCoordinator::frameViewEventTrackingRegionsChanged(FrameView& )200 void AsyncScrollingCoordinator::frameViewEventTrackingRegionsChanged(FrameView& frameView) 200 201 { 201 202 if (!m_scrollingStateTree->rootStateNode()) … … 203 204 204 205 setEventTrackingRegionsDirty(); 206 DebugPageOverlays::didChangeEventHandlers(frameView.frame()); 205 207 } 206 208
Note: See TracChangeset
for help on using the changeset viewer.