Submission errors in +filebug are invisible to users and lead to confusion
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
Bug Description
Symptoms
========
I tried to create a new bug, and in the Tags field, I put in ".my.cnf" (without the quotes). However, when I pressed the "Submit Bug Report" button, a bunch of AJAX-y crap happened, and I was taken back to the first step of creating a new bug. Removing this tag allowed the bug to be created.
Diagnosis
=========
The tag wasn't a valid tag and the bug creation errored appropriately. The resulting page shows no sign of any error until you click on 'No I need to report a new bug' to show the 'There is 1 error' message, and in this case a *further* click, on the advanced options expander, is required to show the detailed error on the tag control.
See also
========
Bug #636188 covers the situation where an error in a control hidden behind an expander is hard to find. This bug is about a step before that - the form as a whole is hidden due to the ajax bug filing workflow.
| Andy Reitz (ajr9) wrote | #1 |
| affects: | launchpad → malone |
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: dupefinder |
| Robert Collins (lifeless) wrote | #3 |
| summary: |
- Tags with '.' in them cause bug submission to fail + Submission errors in +filebug are invisible to users and lead to + confusion |
| description: | updated |
| tags: | added: confusing-ui ui |
| Steve Conklin (sconklin) wrote | #4 |
Here is the bug where I first encountered this issue: https:/