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
Hello, i'm using three.js and metro-ui (v 3.0.13) in a single project. After update to new three.js (v81) i've noticed an interesting bug, particularly here at line 7300 where a method isColor on some object is called. This object can be of different type including string. Metro defines String.prototype.isColor so e.g. 'abc'.isColor would return true. This causes method to fail (i guess three.js doesn't expect isColor on a string). So i just can't use WebGLRenderer with metro-ui.
Is there anything we can do about it? How do you think - should this problem be resolved in metro-ui or three.js (i personally think that in metro-ui)?
The text was updated successfully, but these errors were encountered:
Hello, i'm using three.js and metro-ui (v 3.0.13) in a single project. After update to new three.js (v81) i've noticed an interesting bug, particularly here at line 7300 where a method
isColor
on some object is called. This object can be of different type including string. Metro definesString.prototype.isColor
so e.g.'abc'.isColor
would returntrue
. This causes method to fail (i guess three.js doesn't expectisColor
on a string). So i just can't useWebGLRenderer
with metro-ui.Is there anything we can do about it? How do you think - should this problem be resolved in metro-ui or three.js (i personally think that in metro-ui)?
The text was updated successfully, but these errors were encountered: