RESOLVED FIXED 57651
Behavior of isAccelerated() for a IOSurface-backed canvas should be consistent with accelerated status of its ImageBuffer
https://bugs.webkit.org/show_bug.cgi?id=57651
Summary Behavior of isAccelerated() for a IOSurface-backed canvas should be consisten...
Matthew Delaney
Reported 2011-04-01 12:39:14 PDT
Currently, if a canvas is backed by an IOSurface, its isAccelerated method simply reports whether or not the page settings have canvasUsesAcceleratedDrawing enabled. This leads to an inconsistency because having that preference on isn't a sufficient condition for an accelerated canvas backend (e.g. when the IOSurface backend is avoided due to size limits). Thus, when the canvas is backed by an IOSurface then isAccelerated on the context should only report true when the ImageBuffer is in fact in Accelerated Rendering mode (i.e. it did in fact create an IOSurface backing).
Attachments
Patch (2.08 KB, patch)
2011-04-01 12:46 PDT, Matthew Delaney
simon.fraser: review+
Matthew Delaney
Comment 1 2011-04-01 12:46:57 PDT
Simon Fraser (smfr)
Comment 2 2011-04-01 13:09:51 PDT
Comment on attachment 87899 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=87899&action=review > Source/WebCore/platform/graphics/ImageBuffer.h:89 > + bool isAccelerated() { return m_accelerateRendering; } This should be |const|
Matthew Delaney
Comment 3 2011-04-01 14:00:37 PDT
Note You need to log in before you can comment on or make changes to this bug.