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/5d5711a8-f5a8-4663-8fab-12f95d041d5e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
