NEW312871
[GStreamer][MSE] media/media-source/media-source-seek-to-zero-then-play.html is a permanent failure
https://bugs.webkit.org/show_bug.cgi?id=312871
Summary [GStreamer][MSE] media/media-source/media-source-seek-to-zero-then-play.html ...
Jean-Yves Avenard [:jya]
Reported 2026-04-21 02:26:11 PDT
from bug 312859 ``` --- /sdk/webkit/layout-test-results/media/media-source/media-source-seek-to-zero-then-play-expected.txt +++ /sdk/webkit/layout-test-results/media/media-source/media-source-seek-to-zero-then-play-actual.txt @@ -1,3 +1,5 @@ +FAIL: Timed out waiting for notifyDone to be called + RUN(video.src = URL.createObjectURL(source)) EVENT(sourceopen) @@ -7,16 +9,4 @@ RUN(sourceBuffer.appendWindowEnd = 0.3) Appended first segment with window [0, 0.3) RUN(video.currentTime = 0) -EVENT(seeked) -First seek to 0 completed -RUN(video.currentTime = 0) -EVENT(seeked) -Second seek to 0 completed -RUN(sourceBuffer.appendWindowEnd = 0.6) -Re-appended first segment with window [0, 0.6) -RUN(video.play()) -EVENT(playing) -EXPECTED (video frame rendered past 0.3s) OK -RUN(video.pause()) -END OF TEST ``` seeking to 0 when currentTime is already 0 doesn't fire the `seeked` event which isn't per spec (note that chrome has the same issue). The spec does NOT have an early-abort for seeking to the current position. The seek algorithm always runs through and fires seeking/seeked. The only early-aborts are for readyState == HAVE_NOTHING and no seekable ranges.
Attachments
Note You need to log in before you can comment on or make changes to this bug.