Note that if I add the following:
C#
The page will queue and load for each extra request issued, increasing the time for the loading panel to disappear exponentially (but the panel will stay visible preventing users from interacting with the data being processed).
If instead I add the following:
ASPX
I am limited to a single request at a time and the loading graphic stays up until the associated response is received (but I can't queue up seperate requests from other components on the page).
I'm not saying either of these are true solutions to the issue, but they are work arounds I encountered in attempts to solve it. The real meat of the matter is why are WebKit browsers issuing multiple requests, when IE and Firefox are not. If we can figure that out, we can get a real fix into place.