Extending 'Recommended mark names' to allow user agents to detect media timeouts
@nicjansma is already working on this.
Since Jun 17, 2025.
- Dominant language
- Bikeshed
- Stars
- 31
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
I would like to propose extending performance mark with a recommended mark name for website detected media timeout –
‘mark_media_timeout’, { ‘detail’: {‘error_code’: 1}} so as to allow UA to collect metrics or other diagnostics to help root cause media related performance issues.
Adding context, today media sites detect timeouts and errors while trying to play protected content for APIs like
- CreateMediaKeys
- getVideoPlaybackQuality to detect how long it has taken to decode and present the first frame.
some of these APIs are on the video element while others are related API promises taking too long to resolve.
That is
Problem 1: The breadth of APIs that a UA has to cover to measure media playback timeouts is large.
Problem 2: Secondly it is not trivial to duplicate the website logic on the UA side, for example tracking time to first frame needs additional checks to see if the tab is visible.
Even if the UA has a better implementation to detect time to first frame, being able to validate the media site's perspective of a timeouts and identify discrepancy is useful that having these additional recommended mark names is valuable.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.