New implementations of canvas require putting the canvas into its own layer. When a layout test doesn't dumpAsText and subsequently dumps the render tree, there may be different looking trees depending on which canvas implementation is used. Most (if not all) of the fast/canvas tests have no need to compare the render tree over just using dumpAsText, though most are best used as pixel tests. This patch will change all fast/canvas tests to use layoutTestController.dumpAsText(true) where the 'true' parameter allows for pixel results to also be generated. This solves both issues going forward.
Created attachment 87610 [details] Patch
Comment on attachment 87610 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=87610&action=review I see why you're trying to do this - to avoid differences in the expected results for the different versions. But that makes many of the expected results blank. How do you know if the test passed or failed? Normally you write something to the page to says this which gets put into the expected results. > LayoutTests/fast/canvas/canvas-transform-identity-expected.txt:1 > + I understand the motivation of getting rid of the tree. But shouldn't you at least put in pass/fail messages? What is this test doing? How do you know whether it passed or not? The same is true for results on several other tests here.
My understanding is that most of these tests are only useful as pixel tests since looking at the render tree and seeing a canvas inside of a div doesn't tell you anything anyway (for all these tests that draw something into the canvas, like shadows for example).
Comment on attachment 87610 [details] Patch I see now that these have pixel results. So the expected results are fine.
Committed r82521: <http://trac.webkit.org/changeset/82521>