search

mrdoob / three.js

JavaScript 3D Library.
https://threejs.org/
MIT License
102.81k stars 35.38k forks source link

threejs.org/editor does not save stuff in ff (nightly) #6594

Closed makc closed 9 years ago

makc commented 9 years ago

works in chrome, but nothing happens in ff. no errors in console or anything.

RemusMar commented 9 years ago

I don't use the three.js editor, but I did notice the same issue with opentype.js (typeface.js): The file is saved with Chrome, but not with Firefox (38). For me it looks like a Firefox bug.

makc commented 9 years ago

well, I use filesaver in some of my pages, and it saves the stuff, so... they can fix it.

RemusMar commented 9 years ago

well, I use filesaver in some of my pages, and it saves the stuff, so... they can fix it.

The main question is why Chrome doesn't need workarounds?

makc commented 9 years ago

why Chrome doesn't need workarounds?

seems like ff does not fire clicks for orphan elements.

RemusMar commented 9 years ago

seems like ff does not fire clicks for orphan elements.

Again:

For me it looks like a Firefox bug.

In most of the cases, a workaround is a waste of resources because the real issue is not fixed.

makc commented 9 years ago

but ff and 3js are two different projects. if we want 3js editor to save stuff in ff, we could work around ff issue in 14 minutes, or wait for ff to fix their shit for 14 years, if we aren't lucky. that said, you're free to report the issue there as well.

mrdoob commented 9 years ago

@makc could you double check that my workaround also works?

makc commented 9 years ago

It does. Btw, 'export object' throws TypeError: a is undefined somewhere in three.min.js

mrdoob commented 9 years ago

@makc yeah, I noticed... that one will be tricky to fix...