Decoding "out of order" video frames (IPPP-frames)

[yangfangfang1204]

Here is a stream. I input it in the order of IPPPPP, but the output is not in the same order.
the console log
VideoDecoder.js inputData videoInfo.absTimeStamp:0
VideoDecoder.js inputData videoInfo.absTimeStamp:80
VideoDecoder.js output frame.timestamp:0
VideoDecoder.js inputData videoInfo.absTimeStamp:120
VideoDecoder.js inputData videoInfo.absTimeStamp:200
VideoDecoder.js inputData videoInfo.absTimeStamp:240
VideoDecoder.js inputData videoInfo.absTimeStamp:320
VideoDecoder.js inputData videoInfo.absTimeStamp:360
VideoDecoder.js output frame.timestamp:80
VideoDecoder.js inputData videoInfo.absTimeStamp:440
VideoDecoder.js inputData videoInfo.absTimeStamp:520
VideoDecoder.js output frame.timestamp:120
VideoDecoder.js inputData videoInfo.absTimeStamp:560
VideoDecoder.js inputData videoInfo.absTimeStamp:640
VideoDecoder.js output frame.timestamp:360
VideoDecoder.js output frame.timestamp:200
VideoDecoder.js output frame.timestamp:640

The output of the 200-timestamp frames is later than that of the 360-timestamp frames.

the video file is in [(https://github.com/yangfangfang1204/webcodecs-2/blob/main/webcodecs-outputError.flv)]

[dalecurtis]

Does this reproduce in all browsers or just in say Chromium? If so, please file a bug with the respective browser, this repo is for fundamental / spec issues:

• WebKit (Safari): https://bugs.webkit.org/enter_bug.cgi?product=WebKit&component=Media (WebKit bugzilla account needed).
• Blink (Chrome): https://new.crbug.com/ (Google account needed).
• Gecko (Firefox): https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Audio%2FVideo%3A%20WebCodecs (GitHub or Mozilla Bugzilla account needed).