We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've built vizicities from source, including three.js r71:
The vizi-worker.js is now throwing an error "Uncaught ReferenceError: window is not defined".
... }(), dat.color.toString, dat.utils.common), dat.color.interpret, dat.utils.common), dat.utils.requestAnimationFrame = function() { return window.requestAnimationFrame || window.webkitRequestAnimationFrame || window.mozRequestAnimationFrame || window.oRequestAnimationFrame || window.msRequestAnimationFrame || function(e) { window.setTimeout(e, 1E3 / 60) } }(), dat.dom.CenteredDiv = function(e, a) { ...
Update
Modified the bower.json: "threejs": "*", to "threejs": "r69", - works as advertised again. Also the r70 of three.js is doing it's job.
"threejs": "*",
"threejs": "r69",
It looks like threejs r71 is the problem here.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I've built vizicities from source, including three.js r71:
The vizi-worker.js is now throwing an error "Uncaught ReferenceError: window is not defined".
Update
Modified the bower.json:
"threejs": "*",
to"threejs": "r69",
- works as advertised again.Also the r70 of three.js is doing it's job.
It looks like threejs r71 is the problem here.
The text was updated successfully, but these errors were encountered: