314600 - submit-button in forums doesn't work anymore if using back-button of browser

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Andreas Morawietz]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051031 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051031 Firefox/1.5

If I post something in my forum (or anywhere else!), but there is an error in my post, an errormessage appears.
Now, I want to go back and edit the message. For this reason, I use back-button of my browser.
But then, I CAN'T use the submit-button anymore! It is frozen.





Reproducible: Always

Steps to Reproduce:
1. go to http://www.rettet-unsere-welt.de/forum/index.php?action=vthread&forum=13&topic=258
2. Type in a new post
3. Click on "Beitrag senden", that's the submit button
4. Now go back in browser
5. Submit-button isn't acessable anymore!

Comment 1

[Guy Soffer]

happened to me too.

This used to work in firefox 1.0.7, and fails with 1.5:

http://bookcrossing.com/search

Search for a specific title, then hit back and you'll notice the seach button has stayed in "wait" status, meaning it is effectively frozen.

Comment 2

[Guy Soffer]

Naturally, I forgot the build info :(

Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.8) 
Gecko/20051111 Firefox/1.5

Yours,
    Guy.

Comment 3

[Guy Soffer]

I was talking about this with a friend, and we figured out the problem was probably the Ajax support.

When the back button is hit - the page is reloaded with the form's latest state stored, and this includes the disabled submit button (sites occasioanlly do this to prevent multiple submits).

Comment 4

[Guy Soffer]

Workaround for this bug:

under about:config
set browser.sessionhistory.max_total_viewers to 0
this disables fastback and so solves the problem.

Comment 5

[Andreas Morawietz]

Problem is still there.

Please try it with my new page:

1. go to http://www.energie-bewusstsein.de/forum/index.php?action=vthread&forum=2&topic=121
2. Type in a new post in my guestbook :)
3. Click on "Beitrag senden", that's the submit button
4. Now go back in browser
5. Submit-button isn't accessable anymore!

Comment 6

[Andreas Morawietz]

Hey nobody interested in fixing that bug? I don't have experience to do that, sorry...

Comment 7

[Sam Hills]

I have observed this behavior on several webpages.
Reloading the page allows it to be submitted again.
Changing browser.sessionhistory.max_total_viewers to 0 does not make any difference.

I'm running Mozilla v2.0.0.6 on Windows Server 2003 SP2.

Comment 8

[Jeremy McCracken]

This happens to me to, easy way to reproduce:

1. Go to google.com
2. Type anything in the search bar and hit "Google Search"
3. Click the back button

The Google Search button clicks but nothing happens. Refresh makes it work again. Also, if you very quickly stop the page from loading before it gets to the results page, the button will not work without a refresh.

Using Firefox 2.0.0.9 on Windows XP SP2

Comment 9

[Jeremy McCracken]

There is another report of this same bug, #344420

Comment 10

[Charles Loosen]

See bugs: #316838 , #309993 , #408044

Comment 11

[Paul Laferriere]

See my comment on bug #344420.  I had this problem too but couldn't reproduce it when using a clean profile.  This makes me suspect an extension was to blame.

Comment 12

[Tyler Downer [He/Him]]

This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 13

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.