Moves the recording guidance into the recording-start flow so it appears immediately in-app instead of as a generic Windows warning before the user is ready.
Current Behavior
The recording notice can appear before recording is actually started, and the control flow exposes extra actions that make the start/pause experience harder to follow.
Expected Behavior
Show a friendly in-app acknowledgment as soon as recording starts, require the user to confirm it, and keep the recording controls focused on a single start action.
Steps To Reproduce
Open the library view.
Start a new guide or open an existing one.
Click record.
Observe when the guidance appears and how the recording controls behave.
Proposed Changes or Acceptance Criteria
Show the message from the recording-start path instead of on editor open.
Use an in-app UI element that blends with the app instead of the default Windows warning popup.
Require the user to acknowledge the message before continuing.
Keep the flow immediate when recording begins.
Testing Notes
Ran npm test.
Ran bash tests/run_test.sh.
Screenshots, Logs, or Extra Context
N/A
Deployment / Rollout Notes
No special rollout steps
Documentation only
Other
Notes
None.
Checklist
Scope is limited to the selected area above.
Related docs or comments were updated if needed.
I ran bash tests/run_test.sh.
The PR references a issue number.
Any follow-up work is tracked in TODO.md or an issue.
## Improvement Type
- [x] Improvement
- [ ] Bug
- [ ] Documentation
- [ ] Tests
- [ ] Git / workflow
- [ ] Other
## Issue Type
- [ ] Bug
- [x] Improvement
- [ ] Task
- [ ] Documentation
## Summary
Moves the recording guidance into the recording-start flow so it appears immediately in-app instead of as a generic Windows warning before the user is ready.
## Current Behavior
The recording notice can appear before recording is actually started, and the control flow exposes extra actions that make the start/pause experience harder to follow.
## Expected Behavior
Show a friendly in-app acknowledgment as soon as recording starts, require the user to confirm it, and keep the recording controls focused on a single start action.
## Steps To Reproduce
1. Open the library view.
2. Start a new guide or open an existing one.
3. Click record.
4. Observe when the guidance appears and how the recording controls behave.
## Proposed Changes or Acceptance Criteria
- Show the message from the recording-start path instead of on editor open.
- Use an in-app UI element that blends with the app instead of the default Windows warning popup.
- Require the user to acknowledge the message before continuing.
- Keep the flow immediate when recording begins.
## Testing Notes
- Ran npm test.
- Ran bash tests/run_test.sh.
## Screenshots, Logs, or Extra Context
- N/A
## Deployment / Rollout Notes
- [x] No special rollout steps
- [ ] Documentation only
- [ ] Other
### Notes
None.
## Checklist
- [x] Scope is limited to the selected area above.
- [ ] Related docs or comments were updated if needed.
- [x] I ran bash tests/run_test.sh.
- [x] The PR references a issue number.
- [ ] Any follow-up work is tracked in TODO.md or an issue.
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.
Improvement Type
Issue Type
Summary
Moves the recording guidance into the recording-start flow so it appears immediately in-app instead of as a generic Windows warning before the user is ready.
Current Behavior
The recording notice can appear before recording is actually started, and the control flow exposes extra actions that make the start/pause experience harder to follow.
Expected Behavior
Show a friendly in-app acknowledgment as soon as recording starts, require the user to confirm it, and keep the recording controls focused on a single start action.
Steps To Reproduce
Proposed Changes or Acceptance Criteria
Testing Notes
Screenshots, Logs, or Extra Context
Deployment / Rollout Notes
Notes
None.
Checklist
Pull request closed