| 2010-08-10 19:47:12 |
Andy Reitz |
bug |
|
|
added bug |
| 2010-08-12 14:17:40 |
Henning Eggers |
affects |
launchpad |
malone |
|
| 2010-08-16 13:56:18 |
Deryck Hodge |
malone: status |
New |
Triaged |
|
| 2010-08-16 13:56:21 |
Deryck Hodge |
malone: importance |
Undecided |
High |
|
| 2010-08-16 13:56:30 |
Deryck Hodge |
tags |
|
dupefinder |
|
| 2012-01-05 03:44:31 |
Robert Collins |
description |
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. |
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.
Clicking on 'No I need to report a new bug', then expanding the expander for tags at the bottom will show the error (which is well explained at that point). |
|
| 2012-01-05 03:46:33 |
Robert Collins |
summary |
Tags with '.' in them cause bug submission to fail |
Submission errors in +filebug are invisible to users and lead to confusion |
|
| 2012-01-05 03:50:11 |
Robert Collins |
description |
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.
Clicking on 'No I need to report a new bug', then expanding the expander for tags at the bottom will show the error (which is well explained at that point). |
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. |
|
| 2012-01-05 03:50:24 |
Robert Collins |
tags |
dupefinder lp-bugs |
confusing-ui dupefinder lp-bugs ui |
|
