Strange cart bug

I have been testing my site, and I have just found a very odd bug or behaviour.

If I add two products to my cart, click on the remove box for one of them and update the cart, it then removes that one product leaving me with one left. OK so far, but if I then click on the 'More info' link of the remaining product to visit its detail page, THEN click the back button, the cart removes the one remaining product!

I have also done this to a cart with three or more products, remove one product, click on more info of a product left in the cart, click back and the cart holds one less product again! It's actually deleting the product I have just visited and clicked back on. The browser asks do I want to send the form again?

Why is it removing a product that I didn't check? I assume there is some sort of session issue happening as there is nothing showing in the browser address bar.

Thanks.

when you click the back button, it is resubmitting the update cart button, since that was the action that loaded the page initially.


If you submit a form, go to another page, then click the back button, it resubmits the form, the back button tells the browser to perform the action that loaded the previous page.

Yes, that's what's happening, but I don't have a product checked for removal... is this going to happen regardless of the check button being checked or not?

but you did have an item checked when you initially submitted the form to clear the cart.

When you use the browsers back button, it is submitting the original form.

The remove item behavior uses the line index to determine which item to delete.


This is a drawback of using the browsers back button.

I check an item, click remove, and the cart refreshes to display the remaining products. If I then click through to one of the remaining products' detail page (without checking a further remove button) and click the back button, that product I visited is removed too even though it's remove button isn't checked.

OK, not a problem if it's a browser-based thing rather than a code-based issue. The customer can live with it.

Yes it is a browser based issue.