Bug 89933

Summary: [chromium] Remove dead compositor-related API from GraphicsContext3DPrivate / Extensions3DChromium
Product: WebKit Reporter: James Robinson <jamesr>
Component: New BugsAssignee: James Robinson <jamesr>
Status: RESOLVED FIXED    
Severity: Normal CC: cc-bugs, enne, kbr, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

James Robinson
Reported 2012-06-25 18:29:27 PDT
[chromium] Remove dead compositor-related API from GraphicsContext3DPrivate / Extensions3DChromium
Attachments
Patch (20.10 KB, patch)
2012-06-25 18:30 PDT, James Robinson 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
James Robinson
Comment 1 2012-06-25 18:30:42 PDT
Created attachment 149419 [details] Patch
Kenneth Russell
Comment 2 2012-06-25 18:53:16 PDT
Comment on attachment 149419 [details] Patch Excellent. r=me Can we get rid of any of this stuff from the underlying command buffer implementation? If so, could you file a Chromium-side bug about that? Thanks.
James Robinson
Comment 3 2012-06-25 23:31:23 PDT
No, the compositor is still using it via wgc3d. I expect the compositor will keep using it through one API or another for the foreseeable future.
WebKit Review Bot
Comment 4 2012-06-26 11:09:52 PDT
Comment on attachment 149419 [details] Patch Clearing flags on attachment: 149419 Committed r121268: <http://trac.webkit.org/changeset/121268>
WebKit Review Bot
Comment 5 2012-06-26 11:10:11 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.