-
Notifications
You must be signed in to change notification settings - Fork 2k
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
VideoPress: Newly-converted Video blocks are not playable. #36836
Comments
It is not the first time this issue comes up 🙂. As said in D30868-code, this behavior is intentional:
Should we diverge from what |
Lol, my memory is so short sometimes 🙃 Intentional or not, it's hard not to see it as just broken from a user's point of view 🤔 My first thought was that this should work like nested?inner? blocks, where the first click is the parent (disabled) block, and the second click would be the inner video, with active UI. Looks like this was called Clickthrough, and was disabled for desktop (presumably kept for mobile?), because desktops have enough padding to allow clicking the padding to select the block itself. If all this works as explained, it makes me wonder why the core Video block is disabled; need to play with it. |
Found some context about why Core disables the controls: WordPress/gutenberg#7929 (comment) There is an open issue asking for a better visual on the video controls when they are disabled: WordPress/gutenberg#9252 |
I'm happy to close this in deference to WordPress/gutenberg#9252 then. |
Once a VideoPress block finishes uploading and converting, it displays its UI. However, the UI is inaccessible (it's not possible to click on the Play button for example).
The preview ends up being an iframe within an iframe, which could be related.
The text was updated successfully, but these errors were encountered: