Timeout +filebug on a package
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Critical
|
Unassigned | ||
Bug Description
On the +filebug page
(such as ...//bugs.
if the user takes too long to enter data into that page ("Further information," tags, attachments), then the "Submit Bug Report" button will cause a timeout error message to be displayed. The user could then jump to the conclusion that their research and editing work on the +filebug page has been lost.
The text in the "Further information" field, and possibly the other fields (I didn't check), can be recovered (at least if the user's browser is Firefox) by using the browser's Back button and selecting to file a new bug. The user may still have had a minute or so of stress, though.
Can the timeout be eliminated?
If not, then the user should be warned in advance that only so much time is allotted for entering data into the +filebug page. Maybe a countdown timer could even be shown on the +filebug page itself. The timeout could also be increased (maybe doubled).
Thanks.
| Robert Collins (lifeless) wrote | #1 |
| Changed in launchpad: | |
| status: | New → Incomplete |
| dg1727 (dg1727) wrote | #2 |
| Robert Collins (lifeless) wrote | #3 |
| William Grant (wgrant) wrote | #4 |
| tags: | added: timeout |
| summary: |
- Make +filebug timeouts more user-friendly + Timeout on OOPS-8ad2595f3b87c1950e7be61b39288c46 |
| Changed in launchpad: | |
| status: | Incomplete → Triaged |
| importance: | Undecided → Critical |
| summary: |
- Timeout on OOPS-8ad2595f3b87c1950e7be61b39288c46 + Timeout +filebug on a package |
You can take as long as you want to enter data in the field. What OOPS ID did you get?