Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Thanks Michael. Webworker is impractical - I must support IE - and unnecessary becasue nothing I do takes long enough to notice. The problem is not that success() is not being called, its that the read does not finish EVEN WHEN THERE IS KNOWN DATA TO BE READ. In short, success might be called as much as 8 seconds later than the data became available. I'll check out done() though, and let you know. Commented Jul 5, 2012 at 17:57
  • What I was thinking is that you do a browser check,if its chrome, activate webworker who does a synchronous call. that way you might have a fix for chrome, since only chrome gives issues. Gotta love browser differences. I hope the .done solution works for you. Thats the easiest yo implement. Commented Jul 5, 2012 at 21:58