Account Experience: "Back" button to allow the user to cancel the flow

zepatrik commented 1 year ago

Preflight checklist

[X] I could not find a solution in the existing issues, docs, nor discussions.
[X] I agree to follow this project's Code of Conduct.
[X] I have read and am following this repository's Contribution Guidelines.
[X] This issue affects my Ory Network project.
[X] I have joined the Ory Community Slack.
[X] I am signed up to the Ory Security Patch Newsletter.

Describe your problem

It would be a nice UX to allow going back, even without completing a flow. The browser back button might not always work, e.g. when reauthenticating during a settings flow.

Describe your ideal solution

We probably just want to use the return_to of the flow to render some kind of button that allows the user to trigger this without completing the flow. Stripe has a success and another cancel URL, so we could consider using different URLs there as well.

Workarounds or alternatives

Custom UI.

Version

network

Additional Context

No response

mooro commented 1 year ago

Some user really stuck in situations where only the "Browser back" can be used to return. To prevent this, we are currently opening a new window for the settings page, but this brings other disadvantages. It would be too much effort for us to implement a custom UI just because of this.

github-actions[bot] commented 2 weeks ago

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

open a PR referencing and resolving the issue;
leave a comment on it and discuss ideas on how you could contribute towards resolving it;
leave a comment and describe in detail why this issue is critical for your use case;
open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️

ory / network