NEW 259588
inert embedded video still responds to play/pause key
https://bugs.webkit.org/show_bug.cgi?id=259588
Summary inert embedded video still responds to play/pause key
ataylor32
Reported 2023-07-27 20:44:39 PDT
Created attachment 467144 [details] Demo To reproduce the problem, follow these steps: (1) Open the attached HTML file (2) Start playing the embedded YouTube video (3) Click the "Inert" checkbox to make the embedded YouTube video's iframe inert (4) Press the play/pause key on the keyboard The expected result is that the video should continue playing due to the inert attribute being present on the iframe. The actual result is that the video pauses.
Attachments
Demo (1.09 KB, text/html)
2023-07-27 20:44 PDT, ataylor32
no flags
Eric Carlson
Comment 1 2023-07-28 11:40:35 PDT
(In reply to ataylor32 from comment #0) > > The expected result is that the video should continue playing due to the > inert attribute being present on the iframe. The actual result is that the > video pauses. Why would we want to make it impossible for a user to pause playback? Would it be better to automatically pause when an iframe becomes inert?
ataylor32
Comment 2 2023-07-28 15:53:10 PDT
My use case is I have a <dialog> that I want to be able to be dismissed, but not remove the content of it because the user may reopen it. I have it set up so that when the <dialog> is dismissed, the video within it automatically pauses. But if the user presses the play/pause key on their keyboard, the video starts playing again. I added the inert attribute to prevent this, but that didn't solve the problem.
Radar WebKit Bug Importer
Comment 3 2023-08-03 20:45:13 PDT
Tim Nguyen (:ntim)
Comment 4 2023-08-03 22:20:47 PDT
I think bug 237273 should fix the bug you're seeing by blurring the inert area automatically. Can you test in Safari Technology Preview and see if this still reproduces? https://developer.apple.com/safari/technology-preview/
ataylor32
Comment 5 2023-08-04 13:58:03 PDT
I tested on macOS 13.5 using Safari Technology Preview Release 175 (Safari 17.0, WebKit 18617.1.1.2) and the bug is still present.
Note You need to log in before you can comment on or make changes to this bug.