User Story:

• As a user, I want to use my browsers back button to get back to previous pages
• As a user I want unsurprising behavior of pages I use.

Current Problems: This concerns the first two "pages" in the donation, 1) the amount/payment definition and 2) the address/mail data. Although 1) is filled when people come via banner, they can go to 1) to adjust amount or payment method.

From the point of technology, the first two "pages" are actually just one page but the user sees all the content change, so it is to be treated as a page from the user perspective.

The current lack of pushing to the history stack leads to strange results, like not being able to "go back" to a redefinition of the donation amount or putting the users back to Wikipedia or an empty page if they actually just want to go back on the donation page. This is not only inconvenient to users, but can actually lead to donors accidentally leaving the donation process.

Solution: put page changes like adjusting the donation amount or going from step 1 to step 2 (in case one did not come via a banner) to the browser history stack.

Acceptance Criteria

• Respect the user path:
  • When they hit the back button after first seeing the first step in the form it returns the user to the first step in the form. Eg if the user has hit the modify donation button.
  • When they hit the back button on the second step when coming from a banner they are returned to Wikipedia.
• Analtytics tracks the URLs of the first and second part of the form.

Notes:

• Not having a URL for these steps also breaks analytics.
• A working back button is even more important on mobile, particularly for android users which uses the ← button as a standard shared UI element in apps.
• The back button is already in the browser, so it does not lead to clutter in our website. We should use it to the best of our abilities.