> Could you please request the various security, privacy, enterprise, etc.
bits in your chromestatus entry?

Done!

On Tue, Feb 11, 2025 at 7:40 PM Dale Curtis <dalecur...@chromium.org> wrote:

> Sorry about that. Historically video codec changes were handled via
> internal processes since they were aspects of the underlying Chromium
> platform. Especially so in the case of HEVC where it requires hardware
> support. Going forward all video codec changes will use the Blink process.
>
> - dale
>
> On Tue, Feb 11, 2025 at 9:12 AM Ashley Gullen <ash...@scirra.com> wrote:
>
>> As a web developer interested in Chrome's video encoding capabilities
>> with both WebCodecs and MediaRecorder, I had no idea until reading this
>> that Chrome actually already shipped support for HEVC encoding with
>> WebCodecs in M130 - it doesn't appear to be listed on chromestatus.com.
>> Could Google make sure significant updates like this are noted there?
>> Otherwise important updates can pass us right by!
>>
>> On Tue, 11 Feb 2025 at 16:09, Mike Taylor <miketa...@chromium.org> wrote:
>>
>>> Could you please request the various security, privacy, enterprise, etc.
>>> bits in your chromestatus entry?
>>> On 2/11/25 3:56 AM, 'Markus Handell' via blink-dev wrote:
>>>
>>> CC Dale Curtis as well.
>>>
>>> On Tuesday, February 11, 2025 at 9:56:11 AM UTC+1 Markus Handell wrote:
>>>
>>>> Contact emails:
>>>>
>>>> zhu...@bytedance.com
>>>>
>>>> hand...@google.com
>>>>
>>>> Explainer:
>>>>
>>>> Explainer: Codec support updates for MediaRecorder
>>>> <https://docs.google.com/document/d/1YijhqWaeI118xqZV6Fd-UtqWpGDc-vFfFS6Dg4JEEqc/edit?tab=t.0>
>>>>
>>>> crbug.com/40276507
>>>>
>>>> TAG review:
>>>>
>>>> N/A, small incremental change
>>>>
>>>> Summary:
>>>>
>>>> Support for HEVC platform encoding was added in WebCodecs in Chromium
>>>> M130. As a follow-up, support has been added to the MediaRecorder API in
>>>> Chromium. The API now supports both MP4 and Matroska muxer types with
>>>> different HEVC and H.264 mime type specifications. HEVC encoding is only
>>>> supported if the user's device and operating system provide the necessary
>>>> capabilities.
>>>>
>>>> Link to “Intent to Prototype”
>>>>
>>>> N/A, small incremental change and going directly for shipping.
>>>>
>>>> Risks
>>>>
>>>> Interoperability and Compatibility
>>>>
>>>> Gecko: Firefox 136 recently added support for decoding HEVC videos, see
>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1924066. Standards
>>>> position request link:
>>>> https://github.com/mozilla/standards-positions/issues/1174
>>>>
>>>> WebKit: No official signal but note that MacBooks/iPhones have >95% HW
>>>> encode/decode support of H265 and that Safari has added support for this
>>>> codec in adjacent web APIs such as WebRTC. Standards position request link:
>>>> https://github.com/WebKit/standards-positions/issues/460
>>>>
>>>> Web developers: Positive. Support implemented by ByteDance & Intel.
>>>>
>>>> Will this feature be supported on all six Blink platforms (Windows,
>>>> Mac, Linux, Chrome OS, Android, and Android WebView)?
>>>>
>>>> The support is currently limited to Windows, macOS and Android hosts.
>>>> ChromeOS and Linux support may follow in the future when/if their platform
>>>> codec availability allows.
>>>>
>>>> Is this feature fully tested by web-platform-tests?
>>>>
>>>> Yes, the existing test suite
>>>> <https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/external/wpt/mediacapture-record/>
>>>> was extended with cases for the new codec strings.
>>>>
>>>> Tracking bug
>>>>
>>>> crbug.com/40276507
>>>>
>>>> Link to entry on the Chrome Platform Status
>>>>
>>>> https://chromestatus.com/feature/6375884229181440
>>>>
>>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "blink-dev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to blink-dev+unsubscr...@chromium.org.
>>> To view this discussion visit
>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/edc31811-00da-4410-bfc7-b224bb825e4fn%40chromium.org
>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/edc31811-00da-4410-bfc7-b224bb825e4fn%40chromium.org?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "blink-dev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to blink-dev+unsubscr...@chromium.org.
>>> To view this discussion visit
>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/cb683232-ef5e-47f4-93fa-3e8809a0d2b5%40chromium.org
>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/cb683232-ef5e-47f4-93fa-3e8809a0d2b5%40chromium.org?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJjiFfG4zq4_mUknwsG%2BLetoM_RE1fiqFKVjkAyLJ4GpSUUkCw%40mail.gmail.com.

Reply via email to