Noeri Huisman

> 1. Scene keeps a list of the entities as they attach / remove themselves. This still means that the scene will have to handle on-the-fly insertions and removals on...

Yes, this is no longer needed.

There are currently two iOS specific workarounds in A-Frame related to orientationchange/resize: - [ios-orientationchange-blank-bug.js](https://github.com/aframevr/aframe/blob/master/src/utils/ios-orientationchange-blank-bug.js) - [a-scene.js#L156-L166](https://github.com/aframevr/aframe/blob/master/src/core/scene/a-scene.js#L156-L166) Especially the delayed resize in `a-scene` seems quite similar to the above workaround. I'm...

@dmarcos A-Frame already inject those meta tags ([metaTags.js#L5](https://github.com/aframevr/aframe/blob/master/src/core/scene/metaTags.js#L5)). So either it does not work (anymore?), or we can get rid of one of the two iOS-specific timeout workarounds. Since all...

> Do you think this could also work with a gltf? Yes, it should work with gltf. You can't directly use the material component on a gltf model, so you'd...

This is annoying. In theory all we'd have to do is set `outputEncoding = THREE.LinearSRGBColorSpace` on the WebXR render target. However, this isn't the case for all pre-existing supported devices,...

Uploading the same texture multiple times should always be avoided, especially in the case of video textures. While the use-case of having a single video with various segments/regions might be...

Addressed by https://github.com/aframevr/aframe/pull/5404. It seems the `animation` component tries to prevent zero values by capping at an epsilon. This (unintentionally?) prevented negative scales, but this is no longer needed. So...

@dmarcos Rebased

WebXR support on desktop is sadly very unreliable (see https://github.com/aframevr/aframe/issues/4709). It really only works with a Chromium based browser (with WebXR compiled/enabled) and a properly setup OpenXR runtime. There _should_...