Submission errors in +filebug are invisible to users and lead to confusion

[Andy Reitz]

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)]

Here is the bug where I first encountered this issue: https://bugs.launchpad.net/mylvmbackup/+bug/616033

[Robert Collins (lifeless)]

Still reproducable. I wonder if we have an escaping/security issue latent here.

[Robert Collins (lifeless)]

Ok, we don't, its just a pathological combination of UI glitches.

[Steve Conklin (sconklin)]

The issue for me was that apport submitted a bug with the tags:

apport-bug i386 /usr/bin/python: /home/sconklin/libeagle/libcrypto.so.1.0.0: no version information available (required by /usr/bin/python) /usr/bin/python: /home/sconklin/libeagle/libssl.so.1.0.0: no ver

which apparently included some command line error text.