Hi,
I have been using chrome.desktopCapture.chooseDesktopMedia for over a year which works perfectly and recently tried out chrome.tabCapture.capture. The problem which I came across is the callback which chooseDesktopMedia returns i.e streamId which is getUserMedia() compatible, but in case of chrome.tabCapture.capture the callback returns LocalMediaStream stream object which HAS to be processed in the extension itself.
In case desktopCapture, I am able to send the streamId back to my website js and use it to create RtcPeerConnnection but as I cant pass a complex object like stream to my website js as the message's are JSON.Stringify, I'm forced to move code logic of my website to the extension.
My question : Is this as expected & accepted by the webrtc community ? On one hand we are returning a getUserMedia() compatible streamId and on the other hand we are returning just the stream object which can not be passed back to the website from the extension ?
I searched around a bit and didn't find any bug/change request around this problem. Do we have a roadmap to make this change and return the streamId in case of chrome.tabCapture.capture ?
Regards,
Sagar Pilkhwal