Title: C# Suggestion: Unnecessary double-tap on the Continue button
Severity: Medium
Mode: Lesson
Lesson ID / File: N/A
Environment: Browser (specify version), OS (specify version)
Date/Time: 2026-05-17
Source Code
(Not applicable — UI/UX behavior suggestion)
Steps to Reproduce
Open a lesson in the C# learning module.
Progress through the lesson content.
Press the "Next" button to move to the following lesson.
Expected Output
A single press of the "Next" button should advance to the next lesson immediately.
Actual Output
The button requires a second press to actually move to the next lesson, making the experience feel slow and interrupting the flow.
Suggested Priority
Medium — UX is degraded by unnecessary extra interaction.
Additional Notes
If the lesson consists of just text, advancing should be seamless with one tap. Please review the Continue button event handling and state transition logic.
- **Title:** C# Suggestion: Unnecessary double-tap on the Continue button
- **Severity:** Medium
- **Mode:** Lesson
- **Lesson ID / File:** N/A
- **Environment:** Browser (specify version), OS (specify version)
- **Date/Time:** 2026-05-17
## Source Code
(Not applicable — UI/UX behavior suggestion)
## Steps to Reproduce
1. Open a lesson in the C# learning module.
2. Progress through the lesson content.
3. Press the "Next" button to move to the following lesson.
## Expected Output
A single press of the "Next" button should advance to the next lesson immediately.
## Actual Output
The button requires a second press to actually move to the next lesson, making the experience feel slow and interrupting the flow.
## Suggested Priority
Medium — UX is degraded by unnecessary extra interaction.
## Additional Notes
If the lesson consists of just text, advancing should be seamless with one tap. Please review the Continue button event handling and state transition logic.
You were right that a text-only lesson shouldn't need two taps. The old flow was: Continue marked the tutorial complete and then revealed a separate "Next" button to advance. Completing a tutorial now advances straight to the next unlocked lesson in a single tap. Completion is still acknowledged via the status line and skill-award toasts. If you're on the last lesson of a track (no next lesson), the completion banner stays so you still get the confirmation. Regression tests added; will close once PR #21 merges.
Addressed in spikersoft-angular PR #21.
You were right that a text-only lesson shouldn't need two taps. The old flow was: **Continue** marked the tutorial complete and then revealed a separate **"Next"** button to advance. Completing a tutorial now advances straight to the next unlocked lesson in a single tap. Completion is still acknowledged via the status line and skill-award toasts. If you're on the last lesson of a track (no next lesson), the completion banner stays so you still get the confirmation. Regression tests added; will close once PR #21 merges.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Source Code
(Not applicable — UI/UX behavior suggestion)
Steps to Reproduce
Expected Output
A single press of the "Next" button should advance to the next lesson immediately.
Actual Output
The button requires a second press to actually move to the next lesson, making the experience feel slow and interrupting the flow.
Suggested Priority
Medium — UX is degraded by unnecessary extra interaction.
Additional Notes
If the lesson consists of just text, advancing should be seamless with one tap. Please review the Continue button event handling and state transition logic.
Addressed in spikersoft-angular PR #21.
You were right that a text-only lesson shouldn't need two taps. The old flow was: Continue marked the tutorial complete and then revealed a separate "Next" button to advance. Completing a tutorial now advances straight to the next unlocked lesson in a single tap. Completion is still acknowledged via the status line and skill-award toasts. If you're on the last lesson of a track (no next lesson), the completion banner stays so you still get the confirmation. Regression tests added; will close once PR #21 merges.