A slight update on this issue. It's already been attempted here: https://bugs.webkit.org/show_bug.cgi?id=143561
The issue is that WebKitEFL is using the TextureMapperImageBuffer to run tests on their bots, because the EFL bots don't support OpenGL tests. My suggestion is that we disable accelerated compositing completely for WebKitEFL (if possible) and skip those tests. Once the bots have the ability to run tests that use OpenGL, we can re-enable that code path for WebKitEFL. --Martin On Thu, Apr 23, 2015 at 11:12 AM, Martin Robinson <mrobin...@webkit.org> wrote: > Background: There currently exists a fallback TextureMapper > implementation that does not use OpenGL to composite and project > layers, but instead relies on 2D rasterization. This does not work > correctly for Cairo, since Cairo only supports affine transformations. > I believe this path is only used by GTK+ (and perhaps WinCairo) now. > > Proposal: I would like to remove TextureMapperImageBuffer and make > TextureMapperGL the only implementation of TextureMapper. Not only > will this simplify the code, it will remove a build flag > (TEXTURE_MAPPER_GL). The current path isn't (or really shouldn't) be > enabled by default. > > Please speak up if you are opposed. :) > > --Martin _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
