RESOLVED FIXED 75102
Remove didStartRubberBand and didCompleteRubberBand callbacks 
https://bugs.webkit.org/show_bug.cgi?id=75102
Summary Remove didStartRubberBand and didCompleteRubberBand callbacks
Anders Carlsson
Reported 2011-12-22 11:23:01 PST
Remove didStartRubberBand and didCompleteRubberBand callbacks
Attachments
Patch (10.14 KB, patch)
2011-12-22 11:24 PST, Anders Carlsson 		no flags
DetailsFormatted DiffDiff
Patch (10.53 KB, patch)
2011-12-22 11:41 PST, Anders Carlsson 		aroben: review+
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Anders Carlsson
Comment 1 2011-12-22 11:24:49 PST
Created attachment 120347 [details] Patch
Adam Roben (:aroben)
Comment 2 2011-12-22 11:26:41 PST
Comment on attachment 120347 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=120347&action=review > Source/WebKit2/WebProcess/WebCoreSupport/WebChromeClient.cpp:-766 > -void WebChromeClient::didStartRubberBandForFrame(Frame*, const IntSize&) const > -{ > - m_page->drawingArea()->disableDisplayThrottling(); > -} > - > -void WebChromeClient::didCompleteRubberBandForFrame(Frame* frame, const IntSize& initialOverhang) const > -{ > - m_page->drawingArea()->enableDisplayThrottling(); > -} Why is it OK to remove this code? Your ChangeLog doesn't explain.
Anders Carlsson
Comment 3 2011-12-22 11:41:19 PST
Created attachment 120353 [details] Patch
Anders Carlsson
Comment 4 2011-12-22 11:44:45 PST
Committed r103563: <http://trac.webkit.org/changeset/103563>
Note You need to log in before you can comment on or make changes to this bug.