231414 - Back and forward buttons stop working after resending POSTDATA at sf.net

Status: RESOLVED INVALID

(SeaMonkey :: Location Bar, defect)

Description

[Jared Sutton]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

The Back and the Forward buttons stop functioning after resending the POSTDATA
on the url listed above.

Reproducible: Always

Steps to Reproduce:
1. Go to the url specified 
2. click the 'bugs' link about the center of the screen (i know, it's ironic)
3. click the second 'sort by' list box and choose 'descending'
4. click back on the browser
5. click forward on the browser and click ok on the 'POSTDATA' message

Actual Results:  
The back and the forward buttons no longer function when clicked.


If you go back more than 4 pages in the 'back' history, you can *usually*
continue surfing without a problem, but if you use the forward button to return
to the original page you were at, you'll have the same problem all over again.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Looks like bug 227672, which is fixed in current nightlies but not in 1.6.  If
you could retest with a nightly, that would be great.

Comment 2

[Jared Sutton]

I tried the latest nightly build (2003011908), and the problem still persisted.
 I also found that if you hit refresh on the browser, the back and forward
buttons function again.

Comment 3

[Jared Sutton]

I looked at the information on bug 227672, and tried out the test case.  This
seems to be a different problem.  In that bug, if you hit the back button after
already going back and forward on a resend of the postdata, it will send you to
the wrong page.  In this bug, the back and forward buttons do not function at
all.  Maybe both problems stem from the same origin, but the symtoms are
definitly different.

Comment 4

[Boris Zbarsky [:bzbarsky]]

hmm.. Jared, what are your cache settings?  I get no POSTdata dialog in step 5
of your steps to reproduce...

Comment 5

[Jared Sutton]

I'm using no cache special settings, just the installed defaults.

Comment 6

[Boris Zbarsky [:bzbarsky]]

Could you possibly attach your prefs.js to this bug?

Comment 7

[Jared Sutton]

Attachment: My Prefs.js File

Comment 8

[Jared Sutton]

I tried recreating the situation on my computer again and could not recreate the
problem.  I don't quite understand what happened, but if it works for me and no
one else is having a problem then we should just mark this bug report as invalid.  

Comment 9

[Boris Zbarsky [:bzbarsky]]

Yeah, with that prefs.js I still can't reproduce....  I can't even reproduce the
postdata dialog if I manually set cache size to 0 in the browser.

Please do reopen if this becomes reproducible again, ok?