-
Notifications
You must be signed in to change notification settings - Fork 1
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
Comments
@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. |
breaking the pages isn't an option right now. This needs to be fixed otherwise, or we leave it as is for now |
If we make the nav bar clickable it would prevent a need to use the back
button to some extent.
…On Sep 7, 2017 14:40, "Nurit" ***@***.***> wrote:
breaking the pages isn't an option right now. This needs to be fixed
otherwise, or we leave it as is for now
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#42 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOfPtet2lsh3p-nF3RUyfN-SJqNygYehks5sf9Y0gaJpZM4POZjd>
.
|
Right, but not now. First we launch |
This is an urgent one, @ibanner |
@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. |
(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. |
Reproduce:
Expected result:
Actual result:
Note:
Same logic applies for later or earlier stances.
BACK from Payment page will lead to amount selection instead of details, for example.
The text was updated successfully, but these errors were encountered: