RESOLVED FIXED Bug 82265
[chromium] Add isInputThrottled/didBecomeReadyForAddionalInput to WebWidget to fix input throttling
https://bugs.webkit.org/show_bug.cgi?id=82265
Summary [chromium] Add isInputThrottled/didBecomeReadyForAddionalInput to WebWidget t...
Nat Duca
Reported 2012-03-26 17:09:09 PDT
[chromium] Fix input flow control in threaded compositing mode
Attachments
Patch (17.77 KB, patch)
2012-03-26 17:09 PDT, Nat Duca
no flags
Patch (18.86 KB, patch)
2012-03-26 17:31 PDT, Nat Duca
no flags
oops (18.87 KB, patch)
2012-03-26 17:35 PDT, Nat Duca
jamesr: review+
Nat Duca
Comment 1 2012-03-26 17:09:45 PDT
Nat Duca
Comment 2 2012-03-26 17:11:04 PDT
This is a temporary fix due to M19 timing and this causing jank there. We will fix this properly with 80977
WebKit Review Bot
Comment 3 2012-03-26 17:14:30 PDT
Please wait for approval from abarth@webkit.org, dglazkov@chromium.org, fishd@chromium.org, jamesr@chromium.org or tkent@chromium.org before submitting, as this patch contains changes to the Chromium public API. See also https://trac.webkit.org/wiki/ChromiumWebKitAPI.
WebKit Review Bot
Comment 4 2012-03-26 17:14:54 PDT
Attachment 133933 [details] did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files', u'Source/Platform/ChangeLog', u'Source/Platf..." exit_code: 1 Source/WebCore/ChangeLog:8: You should remove the 'No new tests' and either add and list tests, or explain why no new tests were possible. [changelog/nonewtests] [5] Total errors found: 1 in 21 files If any of these errors are false positives, please file a bug against check-webkit-style.
James Robinson
Comment 5 2012-03-26 17:22:18 PDT
Comment on attachment 133933 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=133933&action=review > Source/WebKit/chromium/ChangeLog:3 > + [chromium] Fix input flow control in threaded compositing mode this isn't terribly descriptive - can you change the title to describe what this patch actually has and put some prose in the body of the ChangeLog describing the expected semantics / flow of these calls? > Source/WebCore/platform/graphics/chromium/cc/CCSingleThreadProxy.cpp:241 > + ASSERT_NOT_REACHED(); what's keeping this from being hit? is the expectation that chromium-side code will only call WebWidget::isInputThrottled() if it is not handling scheduling (i.e. WebWidgetHandlesCompositorScheduling() is true)? if so you should document that on WebWidget. Might be easier to just have this return false and have the chromium code unconditionally check > Source/WebKit/chromium/public/WebWidgetClient.h:77 > + // FIXME: Make pure virtual once upstream deps are satisfied. it doesn't look like anything else in this file is pure virtual
Nat Duca
Comment 6 2012-03-26 17:31:53 PDT
Nat Duca
Comment 7 2012-03-26 17:35:47 PDT
James Robinson
Comment 8 2012-03-26 18:24:21 PDT
Comment on attachment 133939 [details] oops Cool. R=me
Nat Duca
Comment 9 2012-03-26 19:01:58 PDT
Note You need to log in before you can comment on or make changes to this bug.