WebGLRenderer: Do not run window.rAF when in XR.

[Mugen87]

Related issue: Fixed #18666.

Description

I've tested this change with a Oculus Quest (1). When in XR, the animation loop of the window context is now stopped. A check for xr.isPresenting is not necessary anymore.

[marcofugaro]

What about AR examples that still need to render in the animationLoop to run?

three.js/examples/webxr_ar_hittest.html

Line 106 in 56ca942

renderer.setAnimationLoop( render );

[Mugen87]

https://raw.githack.com/Mugen87/three.js/11279449d15a0495adc59204cbcba4a20e2f7fdd/examples/index.html

[Mugen87]

Updated the builds for further testing.

[Mugen87]

There should be no difference compared to prod. When you are currently in XR, the following line prevents that the defined animation callback (which is set via renderer.setAnimationLoop()) is executed in context of window:

three.js/src/renderers/WebGLRenderer.js

Line 939 in 56ca942

if ( xr.isPresenting ) return;

With this PR, the entire window animation loop is stopped and does not run in the background anymore. Hence, the above check can be removed.

[marcofugaro]

Okay! I tested the AR examples and they work the same 🙂

[mrdoob]

Hmm, I think when I did that was because these events were not reliable 🤔
We'll see what happens now 🤞🤓

[mrdoob]

Thanks!