There is no "easy" way to quickly determine if a particular visual action caused some pixels to change on the canvas, so we have to resort to checking every single pixel. On larger canvases, this can take a long time, and the problem is compounded if there are a large number of visual actions in the recording. We should put this behind a setting so that if the user doesn't particularly need/care about `hasVisualEffect` they don't need to suffer the performance hit.
Created attachment 340677 [details] Patch
Comment on attachment 340677 [details] Patch Attachment 340677 [details] did not pass win-ews (win): Output: http://webkit-queues.webkit.org/results/7723773 New failing tests: http/tests/security/contentSecurityPolicy/userAgentShadowDOM/allow-audio.html
Created attachment 340721 [details] Archive of layout-test-results from ews200 for win-future The attached test failures were seen while running run-webkit-tests on the win-ews. Bot: ews200 Port: win-future Platform: CYGWIN_NT-6.1-2.9.0-0.318-5-3-x86_64-64bit
Comment on attachment 340677 [details] Patch r=me
<rdar://problem/40240813>
Comment on attachment 340677 [details] Patch Clearing flags on attachment: 340677 Committed r231981: <https://trac.webkit.org/changeset/231981>
All reviewed patches have been landed. Closing bug.