Re: [mediacapture-handle] Use postMessage pattern for two-way messaging. (#69)

> We also need to stop reinventing postMessage in https://github.com/w3c/mediacapture-handle/issues/11 and https://github.com/w3c/mediacapture-handle/issues/68.

"Need to stop" - **strong wording** there! But an explanation is missing for why we "need" this. Some browsers have shipped Capture Handle and some Web developers have started using it productively. It is unclear to me why we "need" to break the Web through cosmetic changes that confer no benefits.

It's also unclear to me why this issue is in the mediacapture-handle repo. Seems like it belongs in mediacapture-screen-share, given that you're not extending Capture Handle or building on top of it. Rather, you are proposing to replace Capture Handle altogether by your competing proposal. So I [repeat](https://github.com/w3c/mediacapture-handle/issues/68#issuecomment-1310115351) - we should move Capture Handle back to the WICG, given that we have no consensus for it, and given that you don't intend to implement it, and are trying to convince all involved that it should be deprecated in favor of your own proposals.

As for the viability of this mechanism as a replacement - I have [my own proposal](https://github.com/w3c/mediacapture-handle/issues/70) to **extend** Capture Handle with a MessagePort. If you check out the *Challenges* portion of that proposal, you will see why I have a different proposal than yours, and why I think Capture Handle would still be necessary in either case. (To name but one example - your proposal does not work with Conditional Focus.)

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 10 November 2022 14:07:02 UTC