-
Notifications
You must be signed in to change notification settings - Fork 103
Rx.DOM.ready() seems to not work. #106
Comments
I've had the same problem. If I subscribe to The WhatWG HTML Standard Section 12.2.6 "The end" details the order things are supposed to happen in. In short, the order is:
Therefore it is entirely possible that jQuery handles this case correctly by invoking the callback immediately (on next event loop iteration) if In rx.dom.js, if I change:
to
then
I'd submit a pull request for this, but there's currently no test for |
Any update on that? Stumbled over the same issue today. |
according to the MDN documentation, when
document.readyState === 'interactive'
then theDOMContentLoaded
has already fired.The
Rx.DOM.ready()
observable checks to see if thereadyState === 'complete'
, otherwise it listens for theDOMContentLoaded
event. This seems incorrect to me, as the observable will be forever empty if theDOMContentLoaded
event has already fired, and thereadyState === 'interactive'
.The text was updated successfully, but these errors were encountered: