← back to v145 · expose-rtptimestamp-from-webrtc-video-frames-via-videoframe-metadata
conformance · v145
v145 · expose-rtptimestamp-from-webrtc-video-frames-via-videoframe-metadata — conformance probe
5 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
5
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
video-frame-exists |
VideoFrame is exposed — the WebCodecs interface the new metadata() lives on. | exists | … | |
video-frame-metadata-is-function |
VideoFrame.prototype.metadata is a function — the call returns a dictionary that may carry rtpTimestamp. spec ↗ | typeof | … | |
video-frame-metadata-returns-object |
VideoFrame.prototype.metadata() returns an object even for a frame with no native metadata — an empty dictionary in that case. spec ↗ | script | … | |
media-stream-track-processor-exists |
MediaStreamTrackProcessor is exposed — the bridge from WebRTC tracks to VideoFrames, the source of rtpTimestamp-carrying frames. | exists | … | |
rtc-peer-connection-exists |
RTCPeerConnection is exposed — the WebRTC entry point whose received frames carry rtpTimestamp. | exists | … |