Skip to content

Commit 4b23050

Browse files
authored
Merge pull request #275 from jan-ivar/undefinedtimestamp
Have transformer.generateKeyFrame() resolve with undefined
2 parents aeceff8 + 7b4150d commit 4b23050

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

index.bs

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -897,7 +897,7 @@ partial interface DedicatedWorkerGlobalScope {
897897
interface RTCRtpScriptTransformer : EventTarget {
898898
// Attributes and methods related to the transformer source
899899
readonly attribute ReadableStream readable;
900-
Promise<unsigned long long> generateKeyFrame(optional DOMString rid);
900+
Promise<undefined> generateKeyFrame(optional DOMString rid);
901901
Promise<undefined> sendKeyFrameRequest();
902902
// Attributes and methods related to the transformer sink
903903
readonly attribute WritableStream writable;
@@ -1026,7 +1026,7 @@ For any {{RTCRtpScriptTransformer}} named |transformer|, the following steps are
10261026
1. For each |task| in |encoder|.`[[pendingKeyFrameTasks]]`, run the following steps:
10271027
1. If |frame| was generated by a video encoder identified by |task|.`[[rid]]`, run the following steps:
10281028
1. Remove |task| from |encoder|.`[[pendingKeyFrameTasks]]`.
1029-
1. Resolve |task|.`[[promise]]` with |frame|'s timestamp.
1029+
1. Resolve |task|.`[[promise]]` with undefined.
10301030

10311031
By resolving the promises just before enqueuing the corresponding key frame in a {{RTCRtpScriptTransformer}}'s readable,
10321032
the resolution callbacks of the promises are always executed just before the corresponding key frame is exposed.

0 commit comments

Comments
 (0)