3 ms·

It's not a bug, it's using a feature (> 16bits per sample audio) that Firefox doesn't support: https://support.mozilla.org/en-US/kb/html5-audio-and-video-firef

It's not a bug, it's using a feature (> 16bits per sample audio) that Firefox doesn't support: https://support.mozilla.org/en-US/kb/html5-audio-and-video-firefox#w_open-media https://support.mozilla.org/en-US/kb/html5-audio-and-video-f... Sure, it's silly that Firefox doesn't support 24/32bit audio. But it's still Googlers assuming, as usual, that the entire world uses Google products and nothing else. If you can do audio code this impressive, then you can also downsample a waveform.

vlovich123 7y ago
More like all the internal extensions at Google only work on Chrome (most importantly the U2F stuff for authentication which at some point might have better support in the future). That means it's a huge hassle to use a separate browser to even view an internal webpage (as this would be before publishing). Right or wrong this isn't really about the Googlers that wrote this page or did the research but on the IT policy at Google that supports only Chrome. The policy itself isn't necessarily unreasonable either. What would you do given a finite headcount supporting 100k users across the world in all sorts of time zones? I'll also note that IT support at Google is probably the best, smoothest & on top of their game I've experienced having worked at a lot of companies including the biggest ones, so they're doing something right. I wouldn't be surprised though that if this kind of negative feedback reaches this team they'll correct this page + make sure to test such interop issues for media going forward systematically in some way but these kind of blindspots are hard to catch especially when you're using standards that Firefox claims to support (I'll note that Safari doesn't have any issues with the audio).