LG-5213: Reset scroll position on FormSteps content replacements#5552
Merged
LG-5213: Reset scroll position on FormSteps content replacements#5552
Conversation
**Why**: To reflect the fact that content has been replaced, both focus and scroll position should reset to match user expectations that a new page has been presented. This already existed for formalized steps, but was being emulated (incompletely) for in-step content replacements such as capture troubleshooting tips.
zachmargolis
approved these changes
Oct 28, 2021
Contributor
zachmargolis
left a comment
There was a problem hiding this comment.
LGTM, seems simpler overall, love it!
app/javascript/packages/document-capture/components/form-steps.jsx
Outdated
Show resolved
Hide resolved
anniehirshman-gsa
approved these changes
Oct 28, 2021
Contributor
anniehirshman-gsa
left a comment
There was a problem hiding this comment.
Video looks good, thanks for including it!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #5534
Why: To reflect the fact that content has been replaced, both focus and scroll position should reset to match user expectations that a new page has been presented. This already existed for formalized steps, but was being emulated (incompletely) for in-step content replacements such as capture troubleshooting tips. These changes seek to bring consistency to this behavior / implementation.
Video:
output2.mp4