- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Fri, 25 Oct 2024 10:38:08 +0000
- To: public-webrtc-logs@w3.org
> Maybe this is due to the prototype We timeboxed the development of the demo. It was not intended as a professional product, and we intentionally chose to only implement very rudimentary UX. The demo **does** know when forwarding works, and it's even easier after the transition to `captureWheel()`. (I am not sure which part was confusing. If you tell me, I could possibly fix the demo.) The app can trivially track the forwarding state as follows: * Forwarding **starts** after the promise returned by `captureWheel()` resolves. * Forwarding **stops** if: * The app calls `captureWheel(null)`. * The app programmatically stops the capture. * Anything else stops the capture (e.g. the user stops the capture or closes the captured tab). The app knows this through the pre-existing **onended** event handler. Is this not sufficient? -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/19#issuecomment-2437453664 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 25 October 2024 10:38:09 UTC