I'm not sure if this has been discussed before: In my (gwt based) application I'm using "hanging" ajax calls to emulate server push events. This is a common approach to implement realtime notifications from server to browser. Of corse this approach has some drawbacks as it is not suitable for thousands of concurrent users but it might gain more acceptance with upcoming frameworks like comet. This said I've experienced that on Chrome every "hanging" request will not only show the loading page information on the left bottom corner, but also triggers the loading page indicator and the worst part: it also converts the cursor into an hourglass. This kills my application as the user will *always* see the hourglass as there is always a single background connection waiting for server side events. On Firefox and IE these background ajax connections will not change the cursor nor lead to loading page icons.
Cheers, Daniel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
