Hi Ben, thanks for this component. In A-Frame 6.x loading the images by selector doesn't work anymore. Example:

This works:
<a-entity overunder="../assets/witness_painter.jpg"></a-entity>

This doesn't work:
<a-assets> <img id="witness" src="../assets/witness_painter.jpg"> </a-assets> <a-entity overunder="#witness"></a-entity>

My temporary workaround is to change this line
var texture = new THREE.TextureLoader().load( this.data );
to this
var texture = new THREE.TextureLoader().load(this.data.getAttribute('src'));
but this breaks the loading by URL part.

Do you have any idea how to fix this? I'm still new to A-Frame.

In the cardboard-reddit example changing to the next image makes the scene awkwardly freeze for a few seconds.

But the Sep. 23 version does work...

I noticed this during development, not sure what the cause is.

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://imgur.com/xLc3Kj7. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).

For example.

This error does not occur with Chrome or Edge.

The cardboard camera and NVIDIA sample shots look fine, but the large ones seem to get harshly resized.

Other A-frame examples I tried are running great but this has a very "shaky" camera. Seems that my movements with mobile phone are somehow exagerated, too sensitive.