Add data points for Chrome 136 MediaRecorder H26x codec support

[chrisdavidmills]

Summary

Chrome 136 adds support to the MediaRecorder API for HEVC encoding, introducing the hvc1.* codec string, and adds new codecs (hev1.* and avc3.*) supporting variable resolution video in MP4. See https://chromestatus.com/feature/6375884229181440 for more details.

This PR adds a data point for this support to the MediaRecorder() constructor, and to the MediaRecorder.isTypeSupported() static method.

The MediaRecorder.mimeType property is also related, but it only returns a previously-set value rather than setting a MIME type, so I decided to not add a data point there.

Test results and supporting details

Related issues

[github-actions]

Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).

[caugner]

We have not yet decided how to record media codecs, see: #6971

@chrisdavidmills Can you please either add your requirements/thoughts to that issue, or open a separate issue if you prefer so?

[chrisdavidmills]

We have not yet decided how to record media codecs, see: #6971

@chrisdavidmills Can you please either add your requirements/thoughts to that issue, or open a separate issue if you prefer so?

Done

[ddbeck]

This came up on today's BCD call PR triage.

Since this PR opened, we now have a mediatypes data tree. To unblock this PR, I am suggesting the following broad changes:

• If possible, show support for h264 (AVC) and h265 (HEVC) in a new mediatypes.video tree. I'd expect this to represent decoding h264 and h264 (e.g., can you use it in a <video> element). This is probably where the underlying OS support notes would go, if you kept it at all (see a later bullet).

• Being more conventional, structurally, showing support for encoding h264 and h265 with keys like:

  • api.MediaRecorder.MediaRecorder.optons_parameter.mimeType (missing in this PR)
  • api.MediaRecorder.MediaRecorder.optons_parameter.mimeType.hev1_codec (description: codecs=hev1.*)
  • api.MediaRecorder.MediaRecorder.optons_parameter.mimeType.hvc1_codec (description: codecs=hvc1.*)
  • api.MediaRecorder.MediaRecorder.optons_parameter.mimeType.avc3_codec (description: codecs=avc3.*)

• I would suggest omitting the data in api.MediaRecorder.isTypeSupported_static, since the data would have an ambiguous meaning (e.g., is the BCD key to show that you can call isTypeSupported("video/mp4;codecs="codecs=avc3.64003E") without getting an error? Or does it mean that you'll get true?).

• The underlying OS support note seems too vague to be useful. If you have more information (e.g., support on macOS or Linux or whatever), then we have conventional ways of noting that sort of thing (with partials as needed). If you don't have that information, I suggest we just omit it.