Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clicking "Back" from any phase of the donation page takes the user 2 pages back isntead of 1. #42

Open
TheGrandVizier opened this issue Sep 6, 2017 · 7 comments
Milestone

Comments

@TheGrandVizier
Copy link

Reproduce:

  1. Arrive at donations page and click "donate".
  2. Select donation amount.
  3. Proceed to details screen and fill out the details.
  4. Click "Back".

Expected result:

  1. Return to donation amount selection.

Actual result:

  1. Return to main donation page.

Note:
Same logic applies for later or earlier stances.
BACK from Payment page will lead to amount selection instead of details, for example.

@ibanner ibanner self-assigned this Sep 6, 2017
@ibanner
Copy link
Contributor

ibanner commented Sep 7, 2017

@nirgoldberg As you advised me earlier, I've build the entire form on a single page, using JS to display/hide the different stages. I'm not aware of a way for me to "hijack" the browser's BACK button to trigger JS functions - and even if there is one, I'm not sure it's good UX. Please advise?

I could of course break the process to separate pages, but this will take some time.

@nuritgazit
Copy link

breaking the pages isn't an option right now. This needs to be fixed otherwise, or we leave it as is for now

@TheGrandVizier
Copy link
Author

TheGrandVizier commented Sep 7, 2017 via email

@nuritgazit
Copy link

Right, but not now. First we launch

@TheGrandVizier TheGrandVizier added this to the Pergamon milestone Sep 17, 2017
@nuritgazit
Copy link

This is an urgent one, @ibanner

@ibanner
Copy link
Contributor

ibanner commented Jan 21, 2018

@TheGrandVizier To my recollection, in our recent call we said that making the progress bar clickable (#46) will be a good enough solution. If so, this issue should be archived.

@TheGrandVizier
Copy link
Author

(for documentation purposes)

Negative. The back button taking a person 2 pages back is not something I can live with and as far as I am concerned is a major defect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants