You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of r106 all the examples now use es6 modules. I've been told more than once in the last year that some kind of code was unacceptable because it was not IE11 compatible.
But now that all the examples are using import the repo is decidedly not compatible with IE11. In fact it's not compatible with any browser before May 2017.
So, now that someone has finally decided to break compatibility with old browsers how about all rest?
template literals? yes/no
const and let? yes/no
destructuring? yes/no
class keyword? yes/no
Set? Map?
arrow functions
async/await
etc...
The text was updated successfully, but these errors were encountered:
The builds of three.js still work in older browsers. Just migrating the examples to modules has not changed anything about this fact. Hence, I'm not sure it's the right opportunity to revisit this topic.
TBH, instead of creating a new issue, it's be better to continue the discussion here: #6419
As of r106 all the examples now use es6 modules. I've been told more than once in the last year that some kind of code was unacceptable because it was not IE11 compatible.
For example here's one.
I know there are others.
But now that all the examples are using
import
the repo is decidedly not compatible with IE11. In fact it's not compatible with any browser before May 2017.So, now that someone has finally decided to break compatibility with old browsers how about all rest?
const
andlet
? yes/noclass
keyword? yes/noSet
?Map
?etc...
The text was updated successfully, but these errors were encountered: