Suggestion: What about
This has been brought up before but this issue is not unique to WebGL. Apps using the 2d context as well as apps that use just plain HTML both have this issue as well. The example I posted before to show the issue is real was a 2d canvas example and this one is pure HTML.
They are moving stuff around just by repositioning floating DIVs and it has the same problem, it hogs the CPU even when not visible.
This is the WebGL group, not the HTML5 group but it still seems like an opportunity to try to solve this more generally.