Good thing we manually have control over what node-webkit version we use now, then
This is what a Steam rep has to say about it, btw (doesn't sound like they want to change anything on their side just yet):
[quote:cnqap37b]It looks like how they have things setup (maybe a giant canvas or webgl surface) does lead to consistent rendering, so that part actually may be working. Think the actual problem is that they are using the chrome multi-process model and the compositing and gpu rendering are each in a separate process from receiving input. So we inject the overlay hooks into all the processes, but we only find a 3d surface and try to run in the renderer or gpu process but some other process is doing input and we aren’t hooking it.
If they forced the single process model for their webkit/chrome stuff that might make things work without them having to heavily modify the chrome code.