Re: [webkit-dev] TextureMapperGL stencil bug?

Development Subject: Re: [webkit-dev] TextureMapperGL stencil bug? Please also refer to http://trac.webkit.org/changeset/108696. TextureMapperGL works stack based and endClip restores previous stack's clip state. -- Sun On Fri, Aug 1, 2014 at 1:18 AM, Darin Adler mailto:da...@apple.com>

Re: [webkit-dev] TextureMapperGL stencil bug?

Please also refer to http://trac.webkit.org/changeset/108696. TextureMapperGL works stack based and endClip restores previous stack's clip state. -- Sun On Fri, Aug 1, 2014 at 1:18 AM, Darin Adler wrote: > Sounds like you’re probably right. The best way to prove it is to make a > test case to

Re: [webkit-dev] TextureMapperGL stencil bug?

Sounds like you’re probably right. The best way to prove it is to make a test case to demonstrate the problem. It looks like USE(TEXTURE_MAPPER_GL) is currently used as part of the GTK port, so the folks who maintain that port are the most likely to be interested. Please file a bug report

[webkit-dev] TextureMapperGL stencil bug?

Hi, Going through the TextureMapperGL implementation, I see that BeginClip advances the bit plane to the next clipStack().setStencilIndex(stencilIndex * 2); However, EndClip does not revert it back before calling clipStack().applyIfNeeded(m_context3D.get()); The applyIfNeeded disables stencil