| 2010-02-13 18:08:39 |
Andreas Noteng |
bug |
|
|
added bug |
| 2010-02-13 18:08:39 |
Andreas Noteng |
attachment added |
|
screenshot http://launchpadlibrarian.net/39149200/Screenshot-2.png |
|
| 2010-02-13 18:10:29 |
Andreas Noteng |
description |
While triaging bugs my Internet connection went down and I got the attached errormessage while trying to post a comment (not knowing my connection was down)
Running updated lucid, using firefox 3.6. |
While triaging bugs my Internet connection went down and I got the attached errormessage while trying to post a comment (not knowing my connection was down)
Running updated lucid, using firefox 3.6.
The message should say something like: "Connection error", or "Unable to connect to Launchpad". |
|
| 2010-02-13 19:35:35 |
Curtis Hovey |
affects |
launchpad |
lazr-js |
|
| 2010-02-13 19:35:35 |
Curtis Hovey |
lazr-js: importance |
Undecided |
Low |
|
| 2010-02-13 19:35:35 |
Curtis Hovey |
lazr-js: status |
New |
Triaged |
|
| 2010-05-18 10:08:40 |
Deryck Hodge |
bug task added |
|
malone |
|
| 2010-05-18 10:10:41 |
Deryck Hodge |
malone: status |
New |
Triaged |
|
| 2010-05-18 10:10:46 |
Deryck Hodge |
malone: importance |
Undecided |
Low |
|
| 2010-05-18 10:11:09 |
Deryck Hodge |
tags |
|
error-handling errors javascript ui |
|
| 2010-09-15 13:05:25 |
Deryck Hodge |
bug |
|
|
added subscriber Paul Hummer |
| 2010-09-15 13:06:52 |
Deryck Hodge |
tags |
error-handling errors javascript ui |
dhrb error-handling errors javascript ui |
|
| 2010-09-15 13:07:18 |
Deryck Hodge |
malone: importance |
Low |
High |
|
| 2010-09-15 13:07:22 |
Deryck Hodge |
lazr-js: importance |
Low |
High |
|
| 2010-09-15 13:58:06 |
Paul Sladen |
summary |
Uninformative error message |
Uninformative AJAX error messages: provide OOPS and "next step" pointer |
|
| 2010-09-15 14:09:44 |
Paul Sladen |
description |
While triaging bugs my Internet connection went down and I got the attached errormessage while trying to post a comment (not knowing my connection was down)
Running updated lucid, using firefox 3.6.
The message should say something like: "Connection error", or "Unable to connect to Launchpad". |
If the internet connection dies during AJAX submission, or the permission is denied then the client side AJAX flashes up a useless, and uninformative error box with no guidance for the user about what they should /do/ about it. There are main side-effects:
1. The user gets frustrated, puzzled, annoyed (needs reassurance)
2. There is no method (without an OOPS number) to report to the Launchpad devs
3. The user loses their input data effort since they can't resubmit it (needs explanation)
The error dialogue are completely opaque to the user, eg.:
"The following errors were encountered: (,'displayname','launchpad.View')"
where a messages such as:
"Connection error"
"Unable to connect to Launchpad"
or a message indicating server failure (with the returned OOPS number) might be preferable. The message also needs to indicate what the user should /do/. Eg. reconnect and resubmit, report the bug (with direct link to malone/+filebug with subject already filed out as OOPS).
In the case of debugging bug #634847 the inability to get detailed or OOPS information back from the users who were seeing it cost a lot of research time. If the client side Javascript receives an OOPS or other fatal error from the server during an AJAX submission it should deliver this information to the user so that it can be reported.
At a minimum the OOPS should be displayed to the user with the same guidance as the main website error box ("please report this to..."). |
|
| 2010-09-15 14:10:39 |
Paul Sladen |
description |
If the internet connection dies during AJAX submission, or the permission is denied then the client side AJAX flashes up a useless, and uninformative error box with no guidance for the user about what they should /do/ about it. There are main side-effects:
1. The user gets frustrated, puzzled, annoyed (needs reassurance)
2. There is no method (without an OOPS number) to report to the Launchpad devs
3. The user loses their input data effort since they can't resubmit it (needs explanation)
The error dialogue are completely opaque to the user, eg.:
"The following errors were encountered: (,'displayname','launchpad.View')"
where a messages such as:
"Connection error"
"Unable to connect to Launchpad"
or a message indicating server failure (with the returned OOPS number) might be preferable. The message also needs to indicate what the user should /do/. Eg. reconnect and resubmit, report the bug (with direct link to malone/+filebug with subject already filed out as OOPS).
In the case of debugging bug #634847 the inability to get detailed or OOPS information back from the users who were seeing it cost a lot of research time. If the client side Javascript receives an OOPS or other fatal error from the server during an AJAX submission it should deliver this information to the user so that it can be reported.
At a minimum the OOPS should be displayed to the user with the same guidance as the main website error box ("please report this to..."). |
If the internet connection dies during AJAX submission, or the permission is denied then the client side AJAX flashes up a useless, and uninformative error box with no guidance for the user about what they should /do/ about it. There are side-effects:
1. The user gets frustrated, puzzled, annoyed (needs reassurance)
2. There is no method (without an OOPS number) to report to the Launchpad devs
3. The user loses their input data effort since they can't resubmit it (needs explanation)
The error dialogues are completely opaque to the user, eg.:
"The following errors were encountered: (,'displayname','launchpad.View')"
where a messages such as:
"Connection error"
"Unable to connect to Launchpad"
or a message indicating server failure (with the returned OOPS number) might be preferable. The message also needs to indicate what the user should /do/. Eg. reconnect and resubmit, report the bug (with direct link to malone/+filebug with subject already filed out as OOPS).
In the case of debugging bug #634847 the inability to get detailed or OOPS information back from the users who were seeing it cost a lot of research time. If the client side Javascript receives an OOPS or other fatal error from the server during an AJAX submission it should deliver this information to the user so that it can be reported.
At a minimum the OOPS should be displayed to the user with the same guidance as the main website error box ("please report this to...").
|
|
| 2010-09-20 08:30:46 |
Matthew Paul Thomas |
attachment added |
|
screenshot https://bugs.edge.launchpad.net/lazr-js/+bug/521447/+attachment/1612128/+files/Screenshot.png |
|
| 2010-11-30 15:32:40 |
Deryck Hodge |
summary |
Uninformative AJAX error messages: provide OOPS and "next step" pointer |
Bad AJAX error messages: provide OOPS and "next step" pointer |
|
| 2011-03-20 03:05:50 |
Robert Collins |
summary |
Bad AJAX error messages: provide OOPS and "next step" pointer |
ajax errors show 'following errors occured' or a big dump of the html source for the oops page |
|
| 2011-07-07 14:38:16 |
Deryck Hodge |
tags |
dhrb error-handling errors javascript lp-bugs ui |
error-handling errors javascript lp-bugs ui |
|
| 2011-07-07 14:52:52 |
Andrea Corbellini |
bug |
|
|
added subscriber Andrea Corbellini |
| 2012-01-04 03:49:16 |
Robert Collins |
lazr-js: status |
Triaged |
Invalid |
|
| 2012-01-04 03:49:26 |
Robert Collins |
bug task deleted |
lazr-js |
|
|
| 2012-01-05 04:49:38 |
Robert Collins |
marked as duplicate |
|
352000 |
|
