Workaround to support older versions of three.js

Older versions of three.js (until r125) have the following issue
mrdoob/three.js#21126 present which breaks
certain WebXR experiences like "moonrider" and "construct chess".

This workaround makes sure that any WebGL context is marked as XR
compatible when possible which means that applications no longer have
to mark it manually and in the correct order. This fix is verified to
work on both "moonrider" and "construct chess" and also doesn't break
sample WebGL pages that don't use WebXR.

third_party/blink/renderer/modules/webgl/webgl2_rendering_context.cc

@@ -85,12 +85,11 @@ CanvasRenderingContext* WebGL2RenderingContext::Factory::Create(
   // compatible. This scenario occurs if the GPU process is not using the GPU
   // that the VR headset is plugged into. If the GPU process is restarted, the
   // WebGraphicsContext3DProvider must be created using the new one.
-  if (attribs.xr_compatible &&
-      !WebGLRenderingContextBase::MakeXrCompatibleSync(host)) {
-    // If xr compatibility is requested and we can't be xr compatible, return a
-    // context with the flag set to false.
-    attribs.xr_compatible = false;
-  }
+  //
+  // Wolvic: Ignore xr_compatible flag and try to force any context to be XR
+  // compatible. This is a workaround for the following bug in three.js
+  // https://github.com/mrdoob/three.js/issues/21126.
+  attribs.xr_compatible = WebGLRenderingContextBase::MakeXrCompatibleSync(host);
 
   Platform::GraphicsInfo graphics_info;
   std::unique_ptr<WebGraphicsContext3DProvider> context_provider(

third_party/blink/renderer/modules/webgl/webgl_rendering_context.cc

@@ -109,12 +109,11 @@ CanvasRenderingContext* WebGLRenderingContext::Factory::Create(
   // compatible. This scenario occurs if the GPU process is not using the GPU
   // that the VR headset is plugged into. If the GPU process is restarted, the
   // WebGraphicsContext3DProvider must be created using the new one.
-  if (attribs.xr_compatible &&
-      !WebGLRenderingContextBase::MakeXrCompatibleSync(host)) {
-    // If xr compatibility is requested and we can't be xr compatible, return a
-    // context with the flag set to false.
-    attribs.xr_compatible = false;
-  }
+  //
+  // Wolvic: Ignore xr_compatible flag and try to force any context to be XR
+  // compatible. This is a workaround for the following bug in three.js
+  // https://github.com/mrdoob/three.js/issues/21126.
+  attribs.xr_compatible = WebGLRenderingContextBase::MakeXrCompatibleSync(host);
 
   Platform::GraphicsInfo graphics_info;
   std::unique_ptr<WebGraphicsContext3DProvider> context_provider(