1889731 - (hevc-missing) Missing support for HEVC/H265 playback

Status: RESOLVED FIXED

(Web Compatibility :: Knowledge Base, defect)

Description

[Dennis Schubert [:denschub]]

We deliberately do not support HEVC/H265, but let's keep track of cases where this causes interop issues here.

Comment 1

[Alastor Wu [:alwu]]

We've actually added HEVC support (it's still off by default, check the pref media.wmf.hevc.enabled) on Windows, and we have a plan to extend it on other platforms as well.

Comment 2

[Alastor Wu [:alwu]]

BTW You can use bug 1842838 as a place to report HEVC related issues.

Comment 3

[Dennis Schubert [:denschub]]

Thanks for the hint in comment 1. I was aware of the Windows support, but this specific issue was reported on macOS. :) I'm definitely looking forward to that!

(In reply to Alastor Wu [:alwu] from comment #2)

BTW You can use bug 1842838 as a place to report HEVC related issues.

We haven't yet properly announced this yet - but the Web Compatibility :: Knowledge Base component is used in some of our upcoming tooling that helps us estimate the real-user impact of issues. These bugs are a kind of "middleware link" between site-breakage reports either filed on GitHub or here, and their underlying core bugs. Some of the KB bugs can be quite noisy, so we want to avoid making frequent changes to the core bugs. Also, we want to use the priority/severity flags on those bugs for tracking on how many sites this happens, how important those sites are (in terms of site rank/traffic), and also how severe the breakage is (small visual issue vs. a completely broken site), so these KB bugs allow us to change the priority and severity fields without causing some side-effect on the platform engineer work queue.

We'll send out a summary to dev-platform or similar soon(tm).

Comment 5

[Jeff Muizelaar [:jrmuizel]]

HEVC playback doesn't depend on 10bit playback

Comment 6

[Jeff Muizelaar [:jrmuizel]]

We support HEVC in many situations now. Dependent bugs should depend on specific platform bugs like bug 1963910 instead.