Opened 11 months ago
Closed 11 months ago
#1488547 closed Bugs (fixed)
Error Message 'no connection'
| Reported by: | rosali | Owned by: | thomasb |
|---|---|---|---|
| Priority: | 5 | Milestone: | 0.8-stable |
| Component: | User Interface | Version: | 0.8-rc |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Every time when the site gets unloaded while it is still waiting for an response of an AJAX request the GUI throws an error 'no connection'. May be you didn't notice it because the default AJAX request run quite fast. But it is really annoying if you have longer running AJAX requests like the calendar plugin does f.e. for checking reminders.
This happens for me with Chrome.
Attachments (1)
Change History (11)
comment:1 Changed 11 months ago by rosali
comment:2 Changed 11 months ago by thomasb
I can confirm that issue. As you correctly found out, one cannot distinguish connection errors from aborts. So removing that handler would mean that we cannot detect and display real connection errors.
comment:3 Changed 11 months ago by rosali
Nethertheless, I would remove it. It it really confusing for an end user to see these error messages.
comment:4 Changed 11 months ago by alec
I think we could try the method with beforeunload handler from here http://stackoverflow.com/questions/1370322/jquery-ajax-fires-error-callback-on-window-unload
comment:5 Changed 11 months ago by klonos
I'm getting this error with trunk 20120624. Subscribing in order to know when it'll be resolved.
Changed 11 months ago by alec
comment:6 Changed 11 months ago by alec
Please, confirm that attached patch fixes the issue.
comment:7 Changed 11 months ago by rosali
Confirmed - works for me - Thanks, great!
comment:8 Changed 11 months ago by klonos
Yep, fixed! Thanx ;)
comment:9 Changed 11 months ago by alec
- Owner set to thomasb
The "no connection" error message was added in https://github.com/roundcube/roundcubemail/commit/a9c1b877889aea93214a3635be6e652ba74e9f05. The decission to remove this case or to apply the patch is in Thomas's hands.
comment:10 Changed 11 months ago by thomasb
- Resolution set to fixed
- Status changed from new to closed
Patch applied in commit 7794ae1387.

app.js
status is always 'error'. It is never 'abort'.