RESOLVED FIXED Bug 84066
[chromium] Move paintRenderedResultsToCanvas code into DrawingBuffer
https://bugs.webkit.org/show_bug.cgi?id=84066
Summary [chromium] Move paintRenderedResultsToCanvas code into DrawingBuffer
James Robinson
Reported 2012-04-16 13:07:36 PDT
[chromium] Move paintRenderedResultsToCanvas code into DrawingBuffer
Attachments
Patch (5.93 KB, patch)
2012-04-16 13:11 PDT, James Robinson
no flags
tweak checks in DrawingBufferChromium (6.00 KB, patch)
2012-04-16 19:41 PDT, James Robinson
no flags
with more of teh compile (6.00 KB, patch)
2012-04-16 19:45 PDT, James Robinson
no flags
James Robinson
Comment 1 2012-04-16 13:11:15 PDT
James Robinson
Comment 2 2012-04-16 13:20:10 PDT
Tested on the layout tests and by manually checking printing of san angeles and http://trac.webkit.org/export/114291/trunk/LayoutTests/fast/canvas/webgl/webgl-composite-modes.html. On http://trac.webkit.org/export/114291/trunk/LayoutTests/fast/canvas/webgl/webgl-composite-modes.html, after printing the 4 leftmost canvases (preservesDrawingBuffer==false) vanish. This happens with or without this patch.
Adrienne Walker
Comment 3 2012-04-16 18:49:33 PDT
Comment on attachment 137387 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=137387&action=review > Source/WebCore/platform/graphics/chromium/DrawingBufferChromium.cpp:173 > + if (!m_platformLayer || !m_platformLayer->drawsContent()) > + return; This code made more sense in WebGLLayerChromium. Would it make more sense just to check for context lost explicitly than go back to the platform layer, since that really doesn't have anything to do with this function anymore?
James Robinson
Comment 4 2012-04-16 19:13:06 PDT
(In reply to comment #3) > (From update of attachment 137387 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=137387&action=review > > > Source/WebCore/platform/graphics/chromium/DrawingBufferChromium.cpp:173 > > + if (!m_platformLayer || !m_platformLayer->drawsContent()) > > + return; > > This code made more sense in WebGLLayerChromium. Would it make more sense just to check for context lost explicitly than go back to the platform layer, since that really doesn't have anything to do with this function anymore? This check in particular? This check is actually kind of silly - we never get here without having a layer (see WebGLRenderingContext::paintRenderingResultsToCanvas()) and I agree it'd be better to check explicitly for a lost context here.
James Robinson
Comment 5 2012-04-16 19:41:58 PDT
Created attachment 137463 [details] tweak checks in DrawingBufferChromium
James Robinson
Comment 6 2012-04-16 19:45:57 PDT
Created attachment 137465 [details] with more of teh compile
Adrienne Walker
Comment 7 2012-04-16 21:46:23 PDT
Comment on attachment 137465 [details] with more of teh compile R=me.
WebKit Review Bot
Comment 8 2012-04-16 22:37:04 PDT
Comment on attachment 137465 [details] with more of teh compile Clearing flags on attachment: 137465 Committed r114344: <http://trac.webkit.org/changeset/114344>
WebKit Review Bot
Comment 9 2012-04-16 22:37: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.