@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?)
-
-
Replying to @DavidBruant
@DavidBruant@bz_moz@Ms2ger dont think my boss will see it that way :/1 reply 0 retweets 0 likes -
Replying to @DavidBruant
@DavidBruant@bz_moz@Ms2ger@lukas_nowacki got something. It seems to throw that when just _reading_ `HTMLElement.prototype.ownerDocument`1 reply 0 retweets 0 likes -
Replying to @kuvos
@kuvos@bz_moz@Ms2ger@lukas_nowacki That's normal isn't it? HTMLElement.prototype is not a Node instance.2 replies 0 retweets 0 likes -
Replying to @DavidBruant
@DavidBruant@kuvos@bz_moz@ms2ger yes, but should it not just return undefined instead of throwing an exception?2 replies 0 retweets 0 likes -
Replying to @lukas_nowacki
@lukas_nowacki@DavidBruant@bz_moz@Ms2ger +1. what is the recommended way of checking this without triggering a throw? I cant find any.5 replies 0 retweets 0 likes -
Replying to @kuvos
@kuvos@lukas_nowacki@DavidBruant@Ms2ger Your best bet here is in fact a try/catch and then getting people to standardize a useful isNode1 reply 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@lukas_nowacki@DavidBruant@Ms2ger i'd rather see the api NOT throw for regular property reads. make them return a bool or smt.1 reply 0 retweets 0 likes
@kuvos @lukas_nowacki @DavidBruant @Ms2ger That doesn't work in general, unfortunately, because for some props a bool means something.
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.