Yes. I still don't know why Apple is not supporting getUserMedia() in WkWebView which is required for the WebRTC

This radar is active for almost two years now http://www.openradar.me/33571214

I wish you could follow duplicates of radars like in github.. That issue was "resolved" by saying its a duplicate of issue 29281220, which isn't helpful at all. That issue could be even older than the one you linked.

If this is something you care about, you should file an enhancement request, even if you write that it is a duplicate of that issue yourself.

Right now, WKWebView and SFSafariViewController (and the authentication service variant, and Web.app which is used for shortcuts on the home screen) do not have WebRTC support - only MobileSafari.app does.

Apple historically considers dupes as upvotes, so be sure to indicate to which bug you suggest they dupe it if you know of one.

Have they said why they don't just use an upvoting system? Even github kind of has that with the emoji reactions.

No.

November 2016, if you use a prefix search: http://www.openradar.me/29286980

If it's not enabled in web views, there's nothing stopping browsers from polyfilling it with native code.

There is everything stopping you. WKWebView runs in its own process and has very limited options for integrating native code.

The model I was thinking of was native code in the native app, injected polyfill that talks to the native code over a message bus. The native code can draw over the top of the web view and pass messages in. Is there anything in particular stopping that?

I believe the problem is the "message bus" is pretty slow, and has pretty limited throughput, especially for something like audio and video.

IIRC that is exactly what ericsson did, they made a iOS browser that allowed webrtc years before apple by adding functionality to webviews.

Yes there is because you can't implement your own browser engine on iOS. Browsers are just shells for the safari engine on iPhones.

I've heard mixed reports on this - the big issue is technical in that you can't implement your own JIT Javascript engine, because only JavaScriptCore (running out-of-process) can write executable pages.

The big issue is that the app store rules forbid it.

> 2.5.6 Apps that browse the web must use the appropriate WebKit framework and WebKit Javascript.

Where did you get the impression I was suggesting implementing your own browser engine?

The whole point of the discussion surrounds what is possible in web views, not implementing your own browser engine.