fix duplicate asset requests (fixes #2472) #2544
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
One image was causing three requests:
<img>in<a-assets>.crossoriginwasn't set and A-Frame set it for you + re-requested.Changes proposed:
<img>element through all the way down to the Texture creation process so that three.js TextureLoader doesn't get called. All the way down, we handle string (inline URLs) vs. element (<a-assets>).<img>element in THREE.Cache if we use<a-assets>so three.js doesn't ever re-fetch.crossoriginon images because else A-Frame will have to make a second request with thecrossoriginflag set if it's not set.crossOriginon the TextureLoader just in case, we had some reports of it not working for inline URLs