- From: ShijunS via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Oct 2016 16:05:03 +0000
- To: public-media-capture-logs@w3.org
@domenic is largely correct about why we decided to first implement legacy functionalities in WebRTC. We implemented support to createObjectURL for the same reason. However, I don't think createObjectURL should be (re)included into the WG spec. I believe we all wanted the web community to eventually move away from the legacy APIs. In addition, I expect there will be a lot of nuances to have createObjectURL fully defined and have the created url consumable by all consumer objects. Also, from implementation perspective, I'm not confident that all existing implementations behave exactly the same for all use cases. For instance, in Edge, we first implemented srcObject for mediaelement, then realized some sites wouldn't change right away to adopt that, so built an internal polyfill on top of srcObject to support createObjectURL. Clearly this won't scale to all other scenarios or other consumer objects still to be defined. And, we have no plan to invest further along the direction. Btw, the Edge WebRTC implementation discussion should probably go somewhere else :-) -- GitHub Notification of comment by ShijunS Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/404#issuecomment-255417557 using your GitHub account
Received on Friday, 21 October 2016 16:05:11 UTC