youennf

> I said tracks are useless on workers except for this API (i.e., mediacapture-transform) which artificially requires them. This is not artificial, transferring a track to a worker has real...

> Here are some developer requirements that are well known to us and which are ignored by the current version of the spec (not all of these are related to...

> There is nothing magical about FPWDs such that they cannot be improved. Well, we are very far from FPWD, the spec reached consensus within the WebRTC WG and has...

> That there are two implementations doesn't prevent changing the spec to improve it What is proposed is an entire rewriting the API/WebIDL, which means rewriting a large part of...

How does it relate to https://github.com/w3c/mediacapture-transform/issues/113? Should we close one or the other?

Some quick notes: - The difference in code complexity is not that big in these two examples. - For stopping track, I would think the first example to be easier...

When calling getDisplayMedia, the UA will display a UA prompt so that user selects the surface to capture. This is based on this user selection action that activation would happen...

> we essentially want to "forward" the user interaction on a browser surface (which is "the permission prompt" in this case) to the related renderer here. Yes, though the last...

FWIW, restricting to H264, VP8 and VP9 which are in all browsers for now: For VP8 - Chrome has 1 entry (no parameters) - Firefox has 1 entry for VP8...

I do not think the issue is service worker vs dedicated worker but out-of-agent-cluster transfer, which can happen when transferring from a window to another window/dedicated worker/service worker/shared worker. My...