@DavidBruant @bz_moz @Ms2ger dont think my boss will see it that way :/
-
-
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 What are you trying to check?1 reply 0 retweets 0 likes -
Replying to @really_bz
@bz_moz it's a generic check to see if we can get to a `document` object. runs indiscriminately on many objects. whoever made that api... :/1 reply 0 retweets 0 likes -
Replying to @really_bz
@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.1 reply 0 retweets 0 likes
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.