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
I don`t know so much if this is a bug. It is one of those things that makes sense the way it works but introduces some subtle issues into ones application.
When working with jQuery like the example suggests this pops up so it is worth noting in the docs. Objects jQuery return are of the type window.Array window.Object etc and not part of the Node prototype. For example window.$.map returns something that is a window.Array and not an actual Array.
Subtle difference but it could be a while before you notice these things running around you application are not actually Arrays, Objects etc.
I bet this pops up a million more places. I have been hacking at this for a while and it even caught me off guard. Again not so much a bug just a little fact that makes bugs.
:)
The text was updated successfully, but these errors were encountered:
Upon further inspection, the current behavior is correct: we can't let changes to the Node globals interfere with the changes in a given window, or even worse, let changes in one window interfere with changes in another window (which would be the case if they all shared the Node globals).
I don`t know so much if this is a bug. It is one of those things that makes sense the way it works but introduces some subtle issues into ones application.
When working with jQuery like the example suggests this pops up so it is worth noting in the docs. Objects jQuery return are of the type window.Array window.Object etc and not part of the Node prototype. For example window.$.map returns something that is a window.Array and not an actual Array.
Subtle difference but it could be a while before you notice these things running around you application are not actually Arrays, Objects etc.
I bet this pops up a million more places. I have been hacking at this for a while and it even caught me off guard. Again not so much a bug just a little fact that makes bugs.
:)
The text was updated successfully, but these errors were encountered: