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

Allow backtracking to previous group when current group is invalid #540

Open
cpcf opened this issue Feb 24, 2025 · 0 comments · May be fixed by #541
Open

Allow backtracking to previous group when current group is invalid #540

cpcf opened this issue Feb 24, 2025 · 0 comments · May be fixed by #541

Comments

@cpcf
Copy link

cpcf commented Feb 24, 2025

Is your feature request related to a problem? Please describe.

Currently, if the active group in a form has an error, the user is blocked from navigating to a previous group. This can be problematic when resolving the error requires changes to an earlier group.

For example, in the burger example, if I'm entering an order for Frank and encounter a validation issue in the name section, I might decide to go back and change the order for someone else. However, pressing Shift+Tab softlocks the form, preventing backtracking.

Maybe this is intentional, but I’d expect to be able to navigate backward even if the current group has validation issues.

Describe the solution you'd like

Introduce an option to control the strictness of group backtracking. This setting would allow users to override the default behavior, enabling navigation to previous groups even when errors exist in the current group.

Describe alternatives you've considered

Right now, I have to structure forms so that each group is entirely self-contained. This results in overloaded groups and a worse user experience.

Additional context

This issue is especially problematic for field_confirm. If a later group includes a confirmation box and the selected value fails validation, the user is stuck, unable to navigate back to previous groups until they have set the confirm to a valid value.
See: #541

@cpcf cpcf linked a pull request Feb 24, 2025 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant