I'm trying out EventSource:
http://www.html5rocks.com/tutorials/eventsource/basics/
When I open an EventSource connection and leave it open, Chrome's page-
is-loading spinner in the tab spins as long as the connection is open.
Similarly, the user is presented the X for stop button -- the refresh
button never renders. To the user, it looks like the page never fully
loads.
So it seems that for as long as I keep an EventSource connection open,
Chrome doesn't think that the page is loaded, even though I wait to
open the EventSource connection upon DOM ready. If I press the X for
stop button, the EventSource connection closes, which isn't really
what I want.
Is this the correct behavior? When I was using WebSockets, the spinner
wouldn't spin when the socket connection was open.
- Luigi