wire/debug trace breaks IE <= 9

[briancavalier]

The problem is that trace is very aggressive in trying to advise every possible method of every object. This works fine in sane browsers where builtins, like String, are actually real Javascript objects, but breaks in IE where builtins aren't actually Javascript objects, but rather bizarro IE things.

So, for example, if you have a basic type, like a String, in your wire spec, wire/debug will break as it tries to advise the string's methods.

In limited testing, a reasonable workaround seems to be to limit wire/debug to things that are actually objects via the usual Object.prototype.toString.call(thing) === '[object Object]' test (which avoids arrays as well, obviously).

[unscriptable]

it's probably best not to mess with DOM nodes in IE either, so this is probably for the best.

[briancavalier]

Yeah, def. We're already filtering out DOM nodes, thankfully. Interestingly, it's possible to AOP DOM nodes using meld in WebKit! Dunno how useful it would be, though, so yeah, best just to stay away from them across the board for now.

[briancavalier]

Fixed by 6595244