Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353179 - [Client] No retry-dialog when connection is broken
Summary: [Client] No retry-dialog when connection is broken
Status: RESOLVED WORKSFORME
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-27 03:57 EDT by Rüdiger Herrmann CLA
Modified: 2011-11-03 06:11 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rüdiger Herrmann CLA 2011-07-27 03:57:38 EDT
On some computers / operating systems / browsers the dialog that informs the user about a broken connection and offers to retry sending the request doesn't appear.
Instead, the cursor changes to a 'wait-cursor' but the user is still able to interact with the client. This brings client and server out of sync in most cases. The application will most likely be broken when the connection is available again.
Comment 1 Tim Buschtoens CLA 2011-07-28 05:31:54 EDT
I'll need a little more than that. I tried the following on each browser:
-> Launch RAP application server
-> Start RAP application in browser
-> Stop RAP application server
-> Click in browser 
-> "Confirm" message appears ("The server seems to be temporarily unavailable.\nWould you like to retry?")

Tested on Firefox, Chrome, Safari and IE9. 

If the message does not appear, either the request never fails (which would be an issue of qx.io.remote.Request), or Request.js#_isConnectionError doesnt "know" the status code.

In any case i currently have no idea how to reproduce it.
Comment 2 Rüdiger Herrmann CLA 2011-09-12 10:04:55 EDT
(In reply to comment #1)
> [ ... ]
> In any case i currently have no idea how to reproduce it.
The issue can be reproduced on Jochen's computer.
Comment 3 Austin Riddle CLA 2011-09-12 11:02:36 EDT
Hi Tim, 

We also can reproduce this problem in our environment.  Cole thinks that it may be a z-order issue because the browser title bar changes to 'Error Page' even though the dialog is not visible.
Comment 4 Tim Buschtoens CLA 2011-10-31 05:10:54 EDT
Anyone got any more specific into how to reproduce this? Browser/OS/Application/Versions/Steps etc?
Comment 5 Ralf Sternberg CLA 2011-10-31 06:47:51 EDT
Also Jochen cannot reproduce this problem anymore. I'd suggest we close this bug as WORKSFORME and reopen in case we get any new clue.
Comment 6 Ivan Furnadjiev CLA 2011-11-03 06:11:29 EDT
(In reply to comment #5)
> I'd suggest we close this bug as WORKSFORME and reopen in case we get any new clue.