On Mon, Mar 9, 2015 at 10:35 PM, Kenneth Russell <email@example.com> wrote:
Since supporting this feature is the clear direction both for mobile
hardware and WebGL, I'd rather leave this corner case as is rather
than trying to mandate that such loops must fail shader compilation.
Though it would be nice if the constant _expression_ limitation was consistently applied.
Is it a possibility to backport dynamic loop behavior from WebGL 2.0 to WebGL 1.0 via an extension?