Presto Vimeo block causing CLS error and weird display inside Kadence Modal blok
-
Steps to replicate my challenge with Presto Vimeo Video block CLS shift error and weird display inside of Kadence Modal block:
1. On a fresh install of wordpress (https://try[dot]new), install the following plugins; Presto Player free and Kadence blocks pro (to get the Kadence modal block).
2. Create a new post and insert the Presto Vimeo Video block and paste in any Vimeo video URL in the vertical 9:16 aspect ratio. (This is the vimeo video I’ve been testing with https://vimeo[dot]com/943195419)
3. You would visually be able to see in a quick but unmissable flash how the Presto Vimeo Video block moves from the standard 16:9 to the 9:16 aspect ratio video format.
This is how the CLS error comes about when measured in a speed test tool like speedvitals[dot]com.
For reference that this is not a Vimeo problem, you can link the same Vimeo video in the native WordPress Vimeo block and see how it loads directly into the 9:16 aspect ratio at once without going through the 16:9 or horizontal format first.
This is the desired way I want Presto Vimeo Video block to work; to load into 9:16 at once without transforming from the horizontal form first.
4. Now, this is where its really a pain for me. I could live with the Presto Vimeo Video loading from horizontal to vertical, but not the weird, cut-off display inside a Kadence Modal block.
Repeat steps 1-3, but this time, add the Presto Vimeo Video block inside of a Kadence Modal block and preview or publish the page.
While the page is still loading if you quickly scroll to the modal block and open it just in time to watch the Presto Vimeo block transform from horizontal to vertical, the Vimeo video will load just fine as expected.
But then, if you allow the page to load fully and open the modal block, the Presto Vimeo Video will load in half and be cut off at the top, with a large black bar at the bottom.
I’ve tried everything I know but couldn’t get this to work. Presto is a great product and works exceptionally great. I’m sure this is something your devs can just fix without a even blink.
I would be very grateful if you could provide me with instructions, or a custom code, or something to patch this behavior ASAP. Because this is a mission critical matter for my site currently and I may not be able to wait till an update is pushed to fix this for everyone.
Many thanks.
- You must be logged in to reply to this topic.