[chromium] Allow embedder to enter/leave force compositing mode
Created attachment 170809 [details] work in progress
Created attachment 170989 [details] Patch
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.
After discussing with Enne I think the threaded mode solution will look a bit different and won't involve WebWidget interactions. This patch will still work fine for the single threaded path.
Comment on attachment 170989 [details] Patch R=me.
Created attachment 170997 [details] With more null checks so it can be called earlier
Comment on attachment 170997 [details] With more null checks so it can be called earlier R=meagain.
Comment on attachment 170997 [details] With more null checks so it can be called earlier Clearing flags on attachment: 170997 Committed r132708: <http://trac.webkit.org/changeset/132708>
All reviewed patches have been landed. Closing bug.
There are about 15 crashes on each of the bots (Apple-Mac and Apple-Windows) that relate to compositing. http://build.webkit.org/builders/Apple%20Win%207%20Release%20%28Tests%29/builds/29310 It looks like within the regression range that this change is the most relevant. Do you think this could be causing the failures?
> Do you think this could be causing the failures? This code is not compiled for apple-mac or apple-win.