W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > May 2022

Re: [mediacapture-handle] CaptureHandleChangeEvent should just be Event (#50)

From: Elad Alon via GitHub <sysbot+gh@w3.org>
Date: Tue, 03 May 2022 11:24:32 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1115989446-1651577071-sysbot+gh@w3.org>
Let's examine a scenario:
C (capturer) is capturing T (target).
T had long ago set a capture handle H0. C read it. Everything is static for a long time; maybe an hour.
The clock strikes midnight, for **dramatic effect** as well as to simplify timestamps. It's now 00:00:00.
At 00:00:01, T is navigated to a new document. Event E1 is fired on C to clear out the capture-handle.
At 00:00:02, or one second later, the new document finishes loading and executes a call to `setCaptureHandleConfig()`. Event E2 is fired on C to set the new capture-handle, H2.
C's main loop was a bit busy around midnight and only handles E1 at 00:00:04 and E2 at 00:00:06. It actually **ignores** both events. But in between handling E1 and E2 on the queue, at what happens to be 00:00:05, it decides to read the capture-handle through `track.getCaptureHandle()`.
The question boils down to - does it make sense for a browser to give C the capture-handle from 4 seconds ago, rather than the current one?

GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-handle/issues/50#issuecomment-1115989446 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 3 May 2022 11:24:34 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:57 UTC