Bugzilla

(In reply to Nico Grunbaum [:ng] from comment #3)
> Xidorn, WebM containers are only supposed to carry VP8 or VP9 video. [0]
> 
> Bryce, are you aware of any move to support H.264 in WebM in Firefox?
> 
> [0] https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats#WebM

I'm not aware of any plans at this time. I'm going to hold the NI to remind me to discuss this and confirm one way or the other.

(In reply to Xidorn Quan [:xidorn] UTC+10 from comment #4)
> I see.
> 
> But the file is not produced by me. It appears that there is at least some software produces this kind of combination, and Chrome doesn't have problem playing it. It might cause web compatibility issue?
> 
> I'm not sure about interoperability on media... if this is a combination which shouldn't be accepted, should we ask Chrome to remove it?

It would be ideal if other applications didn't create or play such files, since they're not specified (the [webm docs](https://www.webmproject.org/docs/container/) only mention VP8 and 9). It seems production of such files from Chrome's media recorder is [intentional](https://bugs.chromium.org/p/chromium/issues/detail?id=60163) though, so I'm not sure how willing they'd be to change their behaviour there.

(In reply to Nico Grunbaum [:ng] from comment #3)
> Xidorn, WebM containers are only supposed to carry VP8 or VP9 video. [0]
> 
> Bryce, are you aware of any move to support H.264 in WebM in Firefox?
> 
> [0] https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats#WebM

I'm not aware of any plans at this time. I'm going to hold the NI to remind me to discuss this and confirm one way or the other.

(In reply to Xidorn Quan [:xidorn] UTC+10 from comment #4)
> I see.
> 
> But the file is not produced by me. It appears that there is at least some software produces this kind of combination, and Chrome doesn't have problem playing it. It might cause web compatibility issue?
> 
> I'm not sure about interoperability on media... if this is a combination which shouldn't be accepted, should we ask Chrome to remove it?

It would be ideal if other applications didn't create or play such files, since they're not specified (the [webm docs](https://www.webmproject.org/docs/container/) only mention VP8 and 9). It seems production of such files from Chrome's media recorder is [intentional](https://bugs.chromium.org/p/chromium/issues/detail?id=601636) though, so I'm not sure how willing they'd be to change their behaviour there.