Bug 251229

Summary: Mastodon video exits fullscreen immediately in Safari, MiniBrowser assertion failure
Product: WebKit Reporter: Jeff Johnson <opendarwin>
Component: MediaAssignee: Nobody <webkit-unassigned>
Status: NEW ---    
Severity: Normal CC: jer.noble, karlcow, ntim, webkit-bug-importer
Priority: P2 Keywords: BrowserCompat, InRadar
Version: WebKit Local Build   
Hardware: Mac (Apple Silicon)   
OS: macOS 13   
Attachments:
Description Flags
MiniBrowser lldb backtrace none

Description Jeff Johnson 2023-01-26 15:56:27 PST 
Created attachment 464676 [details]
MiniBrowser lldb backtrace

Summary:
There's a video on Mastodon that causes Safari to exit fullscreen as soon as you enter fullscreen. This doesn't happen in Firefox or Google Chrome.

I've tested with Safari 16.3 and Safari Technology Preview Release 162 running macOS Ventura 13.2 and Monterey 12.6.3 on M1 Apple silicon.

I also built WebKit from source (commit 8c0586df02759523c7ba36188adcb4f85a2033de) and tested with MiniBrowser, which hits an assertion failure after the video exits fullscreen. Attached is the lldb backtrace.

Steps to reproduce:
1) Open https://mstdn.plus/@lapcatsoftware
2) Scroll down to the video from https://mstdn.plus/@lapcatsoftware/10974137414728390 on January 23. (Note that the bug doesn't reproduce if you open the post directly, for unknown reasons. You have to use the timeline from step 1.)
3) Open the contextual menu on the video and select Enter Full Screen.

Expected results: The video plays in full screen.

Actual results: The video flashes goes into full screen momentarily, flashes, and exits full screen.
Comment 2 Jeff Johnson 2023-01-26 16:27:46 PST 
I found another example: the YouTube video https://hachyderm.io/@mikeymikey/109758095653559893 on the timeline https://hachyderm.io/@mikeymikey

Again, the bug only occurs if you use the timeline rather than the direct post link.

You can try to enter full screen from the YouTube full screen widget.
Comment 3 Radar WebKit Bug Importer 2023-01-26 16:50:35 PST 
<rdar://problem/104720138>
Comment 4 Alexey Proskuryakov 2023-01-26 16:52:49 PST 
Looks like this assertion is there since 2012 at least:

    ASSERT(m_element);
    if (!m_element)
        return;