This doesn't make sense to me. There's enough content negotiation out there that AV2 will need a new content-type parameter. Feature detection is important to browsers.

▲

shmerl 5 hours ago | parent [-]

I don't think so. WebM doesn't need new content type and it can ship AV1 and VP9 all the same.

▲

jaffathecake 5 hours ago | parent [-]

What are you talking about? Video formats have a whole mad type parameter for this stuff https://jakearchibald.com/2022/html-codecs-parameter-for-av1...

▲

shmerl 2 hours ago | parent [-]

It's not mandatory, and it would work without using it. The whole point is for forward compatibility support effect for sites which are very slow introducing these kind of changes.

▲

jaffathecake an hour ago | parent [-]

It's not mandatory. But if you don't use it, the browser may select a source it cannot play.

	▲	shmerl an hour ago \| parent [-]
		Possibly, but as above, a much slower problem to solve is not in the browser support, but in sites support. Browsers in practice move way faster.