Chris Needham

I would recommend that we create an explainer in any case, as it will help as we go through W3C review process - and TAG will want to see it...

Reopening, as we'll need the explainer when we request TAG review for https://github.com/w3c/autoplay/issues/30. I'll update it to reflect the draft spec API shape and remove the sync/async discussion.

Some things still to add: - Describe the benefit to end-users, not just the benefit to web developers (TAG reviews often look for this) - Explain why we have per-element...

There's now a proposal for HDR support in WebCodecs - see https://github.com/w3c/webcodecs/issues/384.

TC39 discussed Float16Array in their March meeting - see [notes](https://github.com/tc39/notes/blob/main/meetings/2023-03/mar-22.md#float16array-for-stage-2--3).

I have a concern (objection) about the removal of the words "all known" in the current charter template, made in https://github.com/w3c/charter-drafts/pull/415. The original phrasing, which I would prefer to continue...

Many thanks, @irajs! The document here is an early draft, so this is valuable input. Our next task is drafting an API design. Please take a look at https://w3c.github.io/me-media-timed-events/, where...

This is something we should consider in the DataCue spec, as cues could be updated either through application script or by being updated by the UA, e.g., for in-band events....

Discussed 17/5/2021 [minutes](https://www.w3.org/2021/05/17-me-minutes.html). In the DASH event processing mode, discarding repeated equivalent events is an optimisation. In a TextTrack based API for emsg events, we would expect the browser to...

I suggest that we take the document that @irajs provided in https://github.com/WICG/datacue/issues/30 and adjust it to the HTML TextTrack and MSE terminology and use that to document the proposed dispatch...