We have used a lot of time making it work on Safari. And we continue to use quite substantial resources on it. Their webrtc implementation is quite new, and not as stable as Chrome and Firefox. And with new code comes new bugs.
There is currently a bug with audio, where it'll crash in Safari, -- and we have had some issues reconnects that was more our fault (though Firefox and Chrome is much more forgiving). We have a workaround for the first, and will be doing a fix for the second once we're reasonably sure it won't regress other browsers.
Is it any of those issues you talk about? Or is it something else? (I'm not personally familiar with the Safari issues, btw, since I'm a Linux user, but I keep an eye on Firefox and Chromium-based browsers)
