RESOLVED WONTFIX Bug 80977
[chromium] Introduce WebWidgetRenderSurface and WebWidgetScheduler and route input-related throttling through them 
https://bugs.webkit.org/show_bug.cgi?id=80977
Summary [chromium] Introduce WebWidgetRenderSurface and WebWidgetScheduler and route ...
Nat Duca
Reported 2012-03-13 02:20:56 PDT
[chromium] Introduce WebWidgetRenderSurface and WebWidgetScheduler and route input-related throttling through them
Attachments
Patch (32.60 KB, patch)
2012-03-13 02:21 PDT, Nat Duca 		no flags
DetailsFormatted DiffDiff
should build now (32.90 KB, patch)
2012-03-13 02:59 PDT, Nat Duca 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Nat Duca
Comment 1 2012-03-13 02:21:54 PDT
Created attachment 131573 [details] Patch
WebKit Review Bot
Comment 2 2012-03-13 02:25:01 PDT
Please wait for approval from fishd@chromium.org before submitting because this patch contains changes to the Chromium public API. Please wait for approval from fishd@chromium.org, abarth@webkit.org or jamesr@chromium.org before submitting because this patch contains changes to the Chromium platform API.
Nat Duca
Comment 3 2012-03-13 02:26:31 PDT
Here is RenderWidget inversion phase 0. This cleans up some hack-plumbing for fullscreen damage done to turn on scissoring. It then builds up new plumbing for input throttling, which fixes a bug in the threaded compositor where RenderWdiget doesn't properly throttle damaging input acks [because the RenderWidget's paint aggregatoor is empty]. This patch can land as-is. Follow-on patches will start moving more functionality into the scheduler and surface objects.
WebKit Review Bot
Comment 4 2012-03-13 02:39:35 PDT
Comment on attachment 131573 [details] Patch Attachment 131573 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/11942429
Nat Duca
Comment 5 2012-03-13 02:59:36 PDT
Created attachment 131578 [details] should build now
Nat Duca
Comment 6 2012-03-19 13:45:29 PDT
@fishd, ping?
Note You need to log in before you can comment on or make changes to this bug.