lazysizes
lazysizes copied to clipboard
vimeo and domain privacy settings
I really like this simple lazyloading tool and I started to lazy load the hell out of my pages ;)
Everything works fine, but when I use the video-embed plugin in combination with a vimeo video with the domain privacy settings on it doesn't work as expected in Safari. In all other browsers it works perfectly.
Sorry Because of its privacy settings, this video cannot be played here.
Does anybody has the same or similar issue?
Hi @interactivespace,
I seem to have the same issue, not matter what the privacy settings are on Vimeo for this video. Without lazy load, everything works well, but as soon I activate lazysizes on Vimeo videos I've got the following error message on iPhone (only): "Because of its privacy settings, this video cannot be played here."
Does anyone have a fix for this?
Regards, Nico
I have the same issue with Lazy Load Optimizer and WP. All videos on iOS showed the privacy issue (on all browsers). Excluding the URLs with videos fixed the issue.
Just wanted to say thank you to @interactivespace who pointed me in the right direction since I couldn't really figure out what the issue was. Thanks a lot!!
Haven't checked it yet. But does it work with iframeLoadMode
= 1
?
In any case I would need a working test case to check it myself.
Haven't checked it yet. But does it work with
iframeLoadMode
=1
?
for me it fixed bug with vimeo where it didnt have the full screen button, changing the iframeloadmode to 1 seems to fix it thanks a lot
Hi I've got the same problem here https://julienwidmer.webflow.io/home-copy-test-lazyload-290921-23h30# it's working on firefox and chrome, but privacy issue on Safari and all IOS browser..
I've tried also with iframeLoadMode=1, but nothing change.. ( why it would change privacy?)
Is somebody manage to make embed vimeo works on safari and IOS ? is some settings will help to make it work on All browsers/platforms? thanks !!
@aFarkas , my team was able to resolve this on iOS by adding the data-load-mode="1"
attribute to our embedded iframe
element.
I believe this resolves the issue because it affects how the Vimeo resource is retrieved (source).
That is, with load mode 0
, the request to Vimeo is initiated differently than it would be with a standard iframe
. Specifically, I believe it lacks an origin
or referrer
request header (I'm not sure which). Since the request lacks this information, Vimeo responds with a 403 Forbidden
status since it appears as if the video has been embedded on an unauthorized third-party domain.
However, with load mode 1
, the iframe src
attribute is added to the iframe
element, causing the browser to initiate the request in a more typical fashion so that includes the required request headers.