- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Nov 2024 10:55:42 +0000
- To: public-webrtc-logs@w3.org
> My point here is that there are no use cases for detecting the same navigable. It is the wrong solution to a problem. We are not talking same navigable but same surface. There are use case as described above, one more below. More generally, given native applications have this information and make use of it, I do not see why it would not be useful for web pages too. Please also note that surface IDs information already surface in `track.label` for all browsers. > Other alternatives in [w3c/mediacapture-screen-share-extensions#15](https://github.com/w3c/mediacapture-screen-share-extensions/issues/15) seem simpler than overloading `configurationchange` Here is a use case that is better served by `configurationchange`. Let's say I am doing a recording of the screen with microphone. Recording is done via MSTP in a worker. The web application wants to chapterize the recording to easily navigate to specific parts of the recording. Changing of surface is a good event as input for chapterization. Getting the ID of the surface is nice as it can help user skipping to the next time user is sharing the same surface (say user is switching between two different screens, or two windows...). Surface type is a partial solution, surface ID would be good. Also, the web page will want to know when the first video frame of the new surface will happen, to encode it as a key frame and to get its precise timestamp. This issue is not solvable with the callback approach (which has the disadvantage of pausing video frames which we do not want here). One way to solve this is to synchronise settings/configurationchange with the enqueuing of VideoFrames in the worker (same task queue basically). We really need to decide what we do about this synchronisation (ditto with applyConstraints promise resolution). Another solution is to add metadata to VideoFrames. This could end up meaning adding all video track settings to VideoFrame metadata, this can be quite a hammer. I'll file an issue about this. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/308#issuecomment-2485363109 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 November 2024 10:55:42 UTC