Bug 187273

Summary: [GTK] Layout test media/picture-in-picture-interruption.html is timing out
Product: WebKit Reporter: Michael Catanzaro <mcatanzaro>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: bugs-noreply, jer.noble
Priority: P2    
Version: Other   
Hardware: PC   
OS: Linux   

Michael Catanzaro
Reported 2018-07-02 14:49:13 PDT
Layout test media/picture-in-picture-interruption.html is timing out for GTK since it was added in r233360 "Returning PiP'd video to fullscreen while playing leaves video muted." --- /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/media/picture-in-picture-interruption-expected.txt +++ /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/media/picture-in-picture-interruption-actual.txt @@ -1,14 +1,3 @@ -This tests that video is in the correct media session state after ending a background interruption while pipped. +CONSOLE MESSAGE: line 18: TypeError: video.webkitSetPresentationMode is not a function. (In 'video.webkitSetPresentationMode('picture-in-picture')', 'video.webkitSetPresentationMode' is undefined) +FAIL: Timed out waiting for notifyDone to be called -RUN(internals.settings.setAllowsPictureInPictureMediaPlayback(true)) -RUN(video.src = findMediaFile("video", "content/test")) -EVENT(canplaythrough) -RUN(video.play()) -EVENT(playing) -EVENT(webkitpresentationmodechanged) -RUN(internals.beginMediaSessionInterruption("enteringbackground")) -EXPECTED (internals.mediaSessionState(video) == 'Playing') OK -RUN(internals.endMediaSessionInterruption("enteringbackground")) -EXPECTED (internals.mediaSessionState(video) == 'Playing') OK -END OF TEST -
Attachments
Diego Pino
Comment 1 2023-01-25 19:36:37 PST
There are no references to this bug in any TestExpectations. It's probable this bug was solved at some point but it wasn't marked as closed. I'm closing this bug now. If you think this bug report is still valid, please reopen it and add an entry to TestExpectations.
Note You need to log in before you can comment on or make changes to this bug.