Ammo.js debug visualization is broken #4252
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…n requires a secure context. This change fixes it for the local dev server at least.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
/debugcommand used to enable the very useful ammo.js wireframes and other debug visualizations. This code relies on SharedArrayBuffer, which must now run in a secure context, without which you get the following console warning:I'm not confident about the functional or security implications of making this available on a production server, but it looks safe to enable it on the local dev server by adding the required HTTP headers.
Alternative suggestions welcome.
┆Issue is synchronized with this Jira Task