@DavidBruant @bz_moz @Ms2ger I would but I can't figure out what's triggering it :( and debugger refuses to debug due to security (big WTF?)
-
-
@bz_moz of course, we can with try/catch. but since when has that become the preferred way of checking a property :'( -
@kuvos It's been that way forever for DOM props on random objects; the behavior you see almost 15 years old. - 6 more replies
New conversation -
-
-
@bz_moz our case? it would move on because it would obviously not be able to get a document that way :) thing is, right now we _cant_ check. -
@kuvos JS really needs better "branding" stuff so you could check for "is a node". In the meantime, try/catch is really your best bet. :(
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.