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
{{ message }}
This repository has been archived by the owner on Feb 17, 2021. It is now read-only.
Thanks for the info, @Sivakumaresan! Though, seems odd we'd end up in this state, at least if I'm understanding the Hopscotch code correctly. utils.documentIsReady() should only report true if document.readyState is interactive or complete... and so far as I can tell document.body should exist if that's the case (document.body doesn't exist until the browser's done parsing the document). Though, I might be missing something... maybe we need to specifically check for complete instead of also accepting interactive?
Do you have a sample use case that duplicates this behavior? You mention IE 9 and 10 specifically... are those the only two versions where you're seeing this issue?
@zimmi88 I am using IE 10, when the document.readyState is interactive and IE still have the document.body as null. As you mentioned we should probably look only for complete. Yes this issue is only with IE 9 and 10, other browsers works great.
I am getting above error when I test my application in lower versions of IE, document ready is not fired as expected. Can we have a fix for this?
The text was updated successfully, but these errors were encountered: