Hi-- I posted that problem. So far I've been able to find this:
https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSMissingAllowOrigin?utm_source=devtools&utm_medium=firefox-cors-errors&utm_campaign=default which appears to say that the server needs to add a header and then things will work. On Tuesday, January 29, 2019 at 12:53:23 PM UTC-8, Andrey Novoseltsev wrote: > > Similar problem was recently reported on sage-support: > https://groups.google.com/d/topic/sage-support/WotVaKQeanw/discussion > > A solution for a particular page may be to use threejs, but if anybody can > understand what is wrong and what can be done server-side, that would be > awesome. As far as I know it is a relatively recent issue which may be > related to some CORS policy change in browsers. Another possibility is > recent switch to Ubuntu 18.04 (from 16.04) on compute nodes, although I > have no idea how exactly it could create such problems. > > -- You received this message because you are subscribed to the Google Groups "sage-cell" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-cell/e25e2a10-ff98-4abd-9d32-cd04c3769274%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
