Make sure we do not try to run main() before the document has been fully loaded.

Make sure we do not try to run main() before the document has been fully loaded.

The problem was that document.readyState is either loading, interactive,
or complete, so before this change we would sometimes run main() when the
document has been parsed but not fully loaded.

R=efortuna@google.com,vsm@google.com
BUG=
TEST=

Committed: https://code.google.com/p/dart/source/detail?r=9434

[Emily Fortuna, 2012-07-06 10:48:55]

tricky! lgtm.

[vsm, 2012-07-06 10:55:55]

LGTM, but I'll look into replacing this with something safer.

If DOMContentLoaded fires before readyState == complete, main may not run.

[Johnni Winther, 2012-07-09 14:50:02]

This update breaks the behavior on my machine (Windows 7 with Chrome and/or
Firefox). The code finds the document.readyState to 'interactive' but the event
has already been fired, and the event handler is therefore never called.

[vsm, 2012-07-09 14:59:36]

Johnni: This is what I was concerned about.  But, none of our win7 bots (chrome
or ff) have gone red.  Do you have a reliably breaking test case?

On 2012/07/09 14:50:02, Johnni Winther wrote:
> This update breaks the behavior on my machine (Windows 7 with Chrome and/or
> Firefox). The code finds the document.readyState to 'interactive' but the
event
> has already been fired, and the event handler is therefore never called.