100107 2012-10-23 04:11:40 -0700 [CSS Shaders] Remove m_contextSize from the CustomFilterRenderer. 2014-03-02 09:35:09 -0800 1 1 1 Unclassified WebKit Layout and Rendering 528+ (Nightly build) Unspecified Unspecified RESOLVED INVALID P2 Normal --- 98989 0 dongseong.hwang webkit-unassigned krit ralpht+bugs oldest_to_newest 748479 0 dongseong.hwang 2012-10-23 04:11:40 -0700 We would need something like CustomFilterRendererState that will contain the size and other parameters in the future. We should pass that to bindProgramBuffers instead of storing it. There are two reasons. 1. Increase readability as separating changeable values from fixed values including shader program. 2. Be easy to reuse CustomFilterRenderer as making progress css shaders animation. 914176 1 ralpht+bugs 2013-08-02 09:29:26 -0700 In my port, I'm now (sometimes) passing in a custom projection matrix so that I can avoid rendering to a texture and blending that to the framebuffer (which is needlessly wasteful of bandwidth and is too slow on some machines I target). Is your idea that we could also avoid rebinding the attributes and setting uniforms that have not changed since the last render?