Hacker News Reader

Comment by joshmoz | Hacker News Reader

Firefox dev here. Sorry to hear you're having issues with Firefox. This has not been my experience, would love to know more specifics about apps that don't work in Firefox.

Would be hugely helpful if you could file a bug (bugzilla.mozilla.org) when you see something that doesn't work, but if you want a quicker way to help I'll file the bug for you. Just send me a one line email with the problematic URL. joshmoz at gmail

View on HN

Firefox user here, thanks a lot for all the good work!

If I may ask a question while you're here, do you know if there'll be anytime soon an indicator of the degree of security of WebRTC? Right now, I don't think there is any indication if the keys-exchange is done over HTTP for example or other, which is a bit problematic if privacy is important.

Thanks!

afaik, webrtc uses srtp, which is a separate from https.

SRTP/DTLS to be specific instead of SRTP/SDES. In the past the keys were sent in SDP (using SDES--Security Descriptions) therefore over HTTP, but SRTP/DTLS is the way forward and in the spec.

I think it's just something to do with WebRTC, I'll have a better look once I'm home and file a bug. Firefox is still my go-to browser, it's usually just the new stuff that hasn't been implemented yet in the release version that I have issues with.

Thanks for your work! Mozilla's one of my favourite companies!

I am not sure if they are using https://code.google.com/p/webrtc/source/browse/stable/sample... -- it works as a charm on our application.

It seems Firefox's implementation of web audio API is not the same as Chrome or Safari.

Our app that plays audio in sync on multiple devices plays the audio but is out of sync with Safari and Chrome devices.

Any plans to follow safari's and chrome's implementation?

You'll really have to be more specific than that. Firefox's implementation should be standards compliant, from what you said it's impossible to determine if Firefox has a bug, or the app is badly written and relies on non-standards-compliant behavior that only happens to work in WebKit.

If it's the latter, then no, Firefox will not do that.

It's not a problem with the API itself. In Gecko, the time between starting playback and the audio actually beginning is perceivablely greater than in Webkit browsers. It could be resolved by simply delaying start in Gecko, but that's a less than ideal solution.

Reply on news.ycombinator.com