72701 - Bugzilla form contents not restored after using back button if commit has error

Status: VERIFIED DUPLICATE of bug 74639

(Core :: DOM: Navigation, defect, P3)

Description

[Charles Manske]

Load a bugzilla report page in browser.
Type some sample comments in the "Description" field.
Type some bad text such as "badbadbad" in the Keywords field.
Click the Commit button.
You will get the error message that the keyword wasn't recognized.
Use browser's Back button to go back to your page.
Contents in Desctiption field are lost.
Expected result: All of the textfields should contain the same values as they
did before you used "Commit".

I also see this behavior when there is a "midair collision" message because
someone else has commited a change before you.
I also tried using an unrecognized email address in the "CC" field, but in
that case the description was restored ok.
Obviously this is very annoying if you've typed a long and detailed
description for a bug!

Comment 1

[Radha on family leave (not reading bugmail)]

Claudius, can you try this out and provide an update. I'm not sure if there is a
specific problem with the "keywords" form element in bugzilla.

Comment 2

[Claudius Gayle]

the trouble does not seem to be anything specific with the 'keyword' form field.
With a  2001032708 Linux build I attempted to make invalid changes in the 'Add CC',
'QA Contact', and 'keyword' fields combined with an addition to the 'Comments' text field.

In each case I received the bugzilla error page and was told to 'go back'. Upon doing so, I
noted that in each case the 'Comments' text field was blank AND the invalid change I made
was also missing.

This is contrary to 4.x behavior. In that case, after clicking back I was returned to the page as
I left it - comments in the text field AND my invalid changes stood before me, ie all form elements
as I attempted to submit them.

Comment 3

[Radha on family leave (not reading bugmail)]

Marking this dupe of 74639. Thet bug has more people cc'ed on it. I will add 
cmanske to the cc list of that bug. 

*** This bug has been marked as a duplicate of 74639 ***

Comment 4

[Paul Wyskoczka]

The orginal bug has been fixed. Marking verified.