RESOLVED FIXED 87436
[chromium] Add a setForceRenderSurface to WebLayer for test/bench purpose
https://bugs.webkit.org/show_bug.cgi?id=87436
Summary [chromium] Add a setForceRenderSurface to WebLayer for test/bench purpose
Antoine Labour
Reported 2012-05-24 15:51:52 PDT
[chromium] Add a setForceRenderSurface to WebLayer for test/bench purpose
Attachments
Patch (12.42 KB, patch)
2012-05-24 15:52 PDT, Antoine Labour
no flags
Patch for landing (12.28 KB, patch)
2012-05-24 16:28 PDT, Antoine Labour
no flags
Antoine Labour
Comment 1 2012-05-24 15:52:48 PDT
WebKit Review Bot
Comment 2 2012-05-24 15:55:51 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.
Dana Jansens
Comment 3 2012-05-24 15:56:29 PDT
What about just using opacity != 1 with a child layer?
Antoine Labour
Comment 4 2012-05-24 16:00:29 PDT
So that if we ever change the behavior of that (e.g. if this layer doesn't have content, and we only have a single child, we could bubble the opacity down), this still works. Also, changing opacity also means adding blending which has different perf characteristics. It's really a "use a render surface, no questions asked" flag.
Dana Jansens
Comment 5 2012-05-24 16:05:42 PDT
I do admit I've wanted this before :)
James Robinson
Comment 6 2012-05-24 16:07:02 PDT
Comment on attachment 143910 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=143910&action=review Seems good but I'd drop the uncalled getters, personally. > Source/Platform/chromium/public/WebLayer.h:130 > + WEBKIT_EXPORT bool forceRenderSurface() const; Why expose a getter? The caller should know if they've set this or not and if they care track it (I suspect many won't care). Compulsively adding getters everywhere makes me feel a bit like writing I'm writing Java.
Antoine Labour
Comment 7 2012-05-24 16:28:50 PDT
Created attachment 143919 [details] Patch for landing
Antoine Labour
Comment 8 2012-05-24 16:30:51 PDT
(In reply to comment #6) > (From update of attachment 143910 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=143910&action=review > > Seems good but I'd drop the uncalled getters, personally. > > > Source/Platform/chromium/public/WebLayer.h:130 > > + WEBKIT_EXPORT bool forceRenderSurface() const; > > Why expose a getter? The caller should know if they've set this or not and if they care track it (I suspect many won't care). I don't care either way. Removed > Compulsively adding getters everywhere makes me feel a bit like writing I'm writing Java. Nah, that must be because of the coding style ;)
WebKit Review Bot
Comment 9 2012-05-24 18:02:08 PDT
Comment on attachment 143919 [details] Patch for landing Clearing flags on attachment: 143919 Committed r118454: <http://trac.webkit.org/changeset/118454>
WebKit Review Bot
Comment 10 2012-05-24 18:02:13 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.