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

Quiz - Deleting an unsaved section brings the user to a collapsed previous section #12332

Closed
pcenov opened this issue Jun 20, 2024 · 2 comments · Fixed by #12363
Closed

Quiz - Deleting an unsaved section brings the user to a collapsed previous section #12332

pcenov opened this issue Jun 20, 2024 · 2 comments · Fixed by #12363
Assignees
Labels
P0 - critical Priority: Release blocker or regression

Comments

@pcenov
Copy link
Member

pcenov commented Jun 20, 2024

Observed behavior

Observed while testing #12312 - Deleting an unsaved section brings the user to a collapsed previous section which is confusing. There's a TypeError: Cannot read properties of undefined (reading 'questions') in the console.

Video:

Deleting.an.unsaved.section.mp4

Expected behavior

All the questions of the previous section should be visible.

Steps to reproduce the issue

  1. Install the build from First pass string updates following UX writing and ditto review #12312
  2. Observe the steps in the provided video.

Usage Details

Windows 11, Ubuntu 22 - Chrome

@pcenov
Copy link
Member Author

pcenov commented Jun 20, 2024

@radinamatic

@rtibbles
Copy link
Member

Seems like we need to make sure to navigate to the previous section when this happens - I thought I had added logic for this, but perhaps it's not being properly triggered.

@rtibbles rtibbles added the P0 - critical Priority: Release blocker or regression label Jun 20, 2024
@rtibbles rtibbles self-assigned this Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P0 - critical Priority: Release blocker or regression
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants