RESOLVED FIXED 96007
[chromium] Use WebCompositorSupport functions instead of WebCompositor statics
https://bugs.webkit.org/show_bug.cgi?id=96007
Summary [chromium] Use WebCompositorSupport functions instead of WebCompositor statics
James Robinson
Reported 2012-09-06 12:27:15 PDT
[chromium] Use WebCompositorSupport functions instead of WebCompositor statics
Attachments
Patch (44.64 KB, patch)
2012-09-06 12:28 PDT, James Robinson
no flags
for ews (44.66 KB, patch)
2012-09-06 13:53 PDT, James Robinson
no flags
James Robinson
Comment 1 2012-09-06 12:28:57 PDT
James Robinson
Comment 2 2012-09-06 12:29:24 PDT
WebKit Review Bot
Comment 3 2012-09-06 12:30:42 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.
Peter Beverloo (cr-android ews)
Comment 4 2012-09-06 13:25:08 PDT
Comment on attachment 162555 [details] Patch Attachment 162555 [details] did not pass cr-android-ews (chromium-android): Output: http://queues.webkit.org/results/13777289
Adrienne Walker
Comment 5 2012-09-06 13:38:47 PDT
Comment on attachment 162555 [details] Patch R=me. Sounds fine to me, assuming you fix the ews issue.
James Robinson
Comment 6 2012-09-06 13:48:40 PDT
This won't work in a WebKit checkout until the roll in https://bugs.webkit.org/show_bug.cgi?id=96006 lands. Looks like cr-android failed due to a unit test behind an #ifdef, easy to fix (just add the namespace).
James Robinson
Comment 7 2012-09-06 13:53:51 PDT
James Robinson
Comment 8 2012-09-06 16:17:18 PDT
Note You need to log in before you can comment on or make changes to this bug.