The domready events for IE rely on a onreadystatechange to state 'complete'. Normally, this state should go from 'loading', to 'complete' to 'loaded'. However, IE does not always trigger events for all states. Why it skips certain events, I don't know, but it seems related to other content being loaded at the same time. Perhaps IE does not find the time to trigger the event and simply skips a step. If it skips 'loading' or 'loaded', there is no problem, but if it skips 'complete', the domready scripts will never run. I've never seen it skip more than one state, therefore I propose the attached patch, which also checks for 'loaded'.