VR 360, Local HTML file not working in Edge

[ibradley]

Hi everyone

Has anyone created a VR 360 in Animate and managed to open the file in Microsoft Edge?

It will open in Firefox after a 'config origin policy amendment' and also Chrome after adding the '--allow-file-access-from-files' to the exe file path, but I just cant figure out how to get them to work in Edge.

When attempting to do so I'm just presented with a blank white screen.

Our organisation only uses Edge so any ideas would be greatly appreciated!

Many thanks in advance

[kglad]

you should be testing from within animate or upload to a web server and test from there.

[ibradley]

Hi kglad,

yes it works when testing from within Animate, but I need the 360 to work offline (in Microsoft Edge) and so dont have the option of uploading it to a web server unfortunately.

[kglad]

the problem is the way you're testing in edge. don't you see a cross-domain error in the developer console?

[ibradley]

Hi kglad

Apologies, but Im not all that familiar with using the console however, I have attached a screenshot of the error. Do you have any idea how I would need to proceed to make it work? Many thanks in advance.

[kglad]

@ibradley 

yes, that is an expected cross-domain error as mentioned previously.  here's more info, https://www.contentstack.com/docs/developers/how-to-guides/understanding-and-resolving-cors-error/

why aren't you relying on testing with animate.  you can use any browser you want when you test.

[ibradley]

Im experiencing the same issue with this. Its fine when creating and testing the VR 360 in Adobe Animate, but when complete I publish the contents and try running the new HTML file (outside of Animate) it just doesnt load in Microsoft Edge.

So it seems that CORS is in place as a security measure to prevent items like this from loading in browers, but is there a setting in the Edge browser that I can amend to allow my 360s to run (offline and independant of Animate)?

[kglad]

what do you mean by "the same issue with this"?

there's been one issue and that is improper testing.  ie, you don't have a browser problem and you don't have a problem with your animate production files.

if you want to weaken a browser's security settings, google how to do that.  but you've been alerted:  this is not wise and is totally unnecessary.  i believe you misunderstand several things.

[JoãoCésar]

Hi.

If you have to apply special settings for each browser and you cannot rely on Internet, maybe you should consider turning your output into a desktop application using something like Electron or Tauri.

Regards,

JC

[ibradley]

Thanks for your response JC, but unfortuntely running executables isnt an option in our work place either.