Skip to content

possible fix for recording issue#240

Open
PL00T00 wants to merge 2 commits into
hackclub:mainfrom
PL00T00:fix/chromium-recording-gesture
Open

possible fix for recording issue#240
PL00T00 wants to merge 2 commits into
hackclub:mainfrom
PL00T00:fix/chromium-recording-gesture

Conversation

@PL00T00

@PL00T00 PL00T00 commented Jun 29, 2026

Copy link
Copy Markdown

Summary

Surface Linux/browser screen-capture failures instead of silently bouncing the user back into the source-selection flow.

Why

On some Linux Chromium setups, the user can complete the source picker but the browser never hands the app a usable stream, or the stream ends immediately. The previous flow made that look like an infinite loop back to the picker.

This matches the reported Arch/Linux behavior much better than a pure user-gesture issue.

Change

  • surface browser screen-capture failures on the mode selector instead of silently restarting
  • treat deliberate screen-picker cancellation separately from real capture failure
  • preserve the specific failure reason so the UI can warn the user and steer them toward Desktop
  • show inline camera-start errors instead of lumping them into the same silent restart path

Verification

  • ran npx pnpm --filter @lapse/lapse-client check-types

@PL00T00 PL00T00 force-pushed the fix/chromium-recording-gesture branch from 6debf76 to 59f517a Compare July 1, 2026 11:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants