I&#x27;m too tired to look it up right now (I&#x27;m in DC, check the news), but I believe the WebVR implementations are trying to remove triple-buffering, because entire frames of latency are bad news. I don&#x27;t want to put words in Brandon Jones&#x27; mouth, but I seem to remember him talking about having it implemented in Chrome, which came part-and-parcel with unhinging requestAnimationFrame from the &quot;default&quot; refresh rate of 60hz and using the actual, target display&#x27;s refresh rate. Mozilla apparently has some hurdles to get over before it&#x27;s able to do this, so Firefox is lagging in a pure performance standpoint (though it is slightly more stable).