Removing onContinue redirect from the default close button in Legacy Dialog #44969
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.
The major update of this PR: when a user presses the x button on the legacy dialog feedback/finish popup, instead of being redirected to the next level, the dialog closes. This was updated in a recent pr for the level type dance (jira ticket: https://codedotorg.atlassian.net/browse/LP-2192).
This is a simplification, removing the variable 'hideButDontContinue' entirely, as well as the onContinue() default from the onHidden function.
AI lab and fish are the only level types with their own onContinue() functions that report progress: neither of these uses a dialog at all, so progress will not be lost when removing this default here.
Links
Testing story
There is now a series of steps in hour_of_code.feature to verify that when the x button is pressed in the legacy dialog, you remain on the same page instead of moving to the next level in a redirect. The other tests remain unchanged, but are updated so that the user must press the continue button to move to the next level.
Deployment strategy
Follow-up work
Privacy
Security
Caching
PR Checklist: