Composited/HW content have the red and blue channels inverted in DRT on Chromium Android. To list a few examples: * http://build.webkit.org/results/Chromium%20Android%20Release%20(Tests)/r130632%20(1228)/css3/filters/effect-drop-shadow-hw-diffs.html Test: http://trac.webkit.org/export/130632/trunk/LayoutTests/css3/filters/effect-drop-shadow-hw.html * http://build.webkit.org/results/Chromium%20Android%20Release%20(Tests)/r130632%20(1228)/compositing/shadows/shadow-drawing-diffs.html Test: http://trac.webkit.org/export/130632/trunk/LayoutTests/compositing/shadows/shadow-drawing.html This also seems to happen to text content, such as in this result: * http://build.webkit.org/results/Chromium%20Android%20Release%20(Tests)/r130632%20(1228)/compositing/sibling-positioning-diffs.html Test: http://trac.webkit.org/export/130632/trunk/LayoutTests/compositing/sibling-positioning.html Normal images and texts are fine. As a point of interest here, the red and blue channels are being inverted by code in DumpRenderTree itself, but it seems that normal (non-accelerated) screenshots also take this path. http://code.google.com/searchframe#OAMlx_jo-ck/src/third_party/WebKit/Tools/DumpRenderTree/chromium/TestShell.cpp&l=676 Could it be that the SkCanvas in m_webViewHost->canvas() returns BGRA for hardware, RGBA for software paths?
I don't think it is a Skia issue as the SW skia backend is used for at least the third test (and possibly the second as well). I'd guess it has to do with invoking the compositor.
I seem to remember Alok ran into a channel swap in the compositor someplace. Don't know if it was related.
I'm guessing there's a mismatch between the compositor's read back pixel format and what Skia/WebViewHost is expecting. We've had a few of these before so it's not entirely unlikely.
Created attachment 170652 [details] Patch
Comment on attachment 170652 [details] Patch Hmm, so the byte order for kARGB_8888 is different on android, or the configuration itself is different?
The macros SK_R32_SHIFT, SK_G32_SHIFT, etc that define the byte order of Skia's kARGB_8888 are set differently on Android than on other platforms.
Comment on attachment 170652 [details] Patch OK, thanks for the clarification. Patch seems fine but I have a sneaking suspicious that this might not be the only place we have byte order problems.
Comment on attachment 170652 [details] Patch Clearing flags on attachment: 170652 Committed r132518: <http://trac.webkit.org/changeset/132518>
All reviewed patches have been landed. Closing bug.