-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Video Block: Make users aware about Autoplay and Muted combination #69218
Comments
This comment has been minimized.
This comment has been minimized.
Hi @yogeshbhutkar, I believe @Rishit30G is referring to the fact that newer versions of mobile browsers on Android and iOS do support the autoplay function. However, it only works when the video is muted or has no audio channel: Screen.Recording.2025-02-17.at.3.55.29.PM.movWhen muted is on: Screen.Recording.2025-02-17.at.3.58.29.PM.movReference - https://webkit.org/blog/6784/new-video-policies-for-ios/ |
Thanks for the clarification! |
Thanks both for looking into it, appreciate your efforts! 🙇🏻
Yes, I'm also coming from the same references and I believe they have been considered while building this block, and if they are then we should assist the user to use the functionality as intended. However some more expert eyes can suggest some better insights for this one 👀 |
I think the auto play option should be disabled until muted is enabled. |
Thank you for your suggestion 🙇🏻 |
Description
Currently, we don’t have a way to inform users that autoplay and muted must be enabled together for the video to play. As it stands, if a user enables the autoplay toggle, the video does not play on the frontend unless muted is also enabled.
To improve clarity, it would be helpful to provide users with a short description when they toggle the autoplay switch, informing them that autoplay only works when the video is muted.
Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
Screen.Recording.2025-02-17.at.1.02.09.PM.mov
Environment info
Please confirm that you have searched existing issues in the repo.
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Please confirm which theme type you used for testing.
The text was updated successfully, but these errors were encountered: