Current status?

[tracend]

Thanks for creating this, it's been over three years already!

I have to admit that at first I rejected the implementation because I felt the browser vendors would be fast to support CSS shaders, and a polyfil-type library didn't seem necessary...

I was wrong. 2016 is coming and full support for CSS shaders is still a distant reality.

Obviously not enough people have bumped into this limitation to make it a priority; although that may change soon, as the browser is used more like a game engine viewport.

Having said that, what is your take on the issue based on your experience and how do you feel about using your library today? Any missing features you'd like to see PRs for?

Cheers

[niklasvh]

This was more of just an experiment, and as you mentioned, the CSS shaders development seemed to have stalled.

The biggest issue with this library is that it doesn't react to DOM mutations, so it isn't all that practical really.

[tracend]

Understand, the work you've done here is a good exhibition of how to circumvent browser support but integrating it as is to a production app could become a challenge.

Still, shader support (outside WebGL) is so important if we want the DOM to participate in a meaningful way (visually) in our multimedia creations.

At the moment I'm investigating a performant solution for the common VR fisheye effect, as everything I have is dragging performance down, and using CSS shaders would be a no-brainer.

Thanks again.