graciousfilms.com - Embedded Vimeo video player issues

[back2themoon]

Unless I'm mistaken, there are still some unresolved issues with Vimeo? Anyway, some embedded Vimeo players work as expected. This one doesn't.

Visit: https://www.graciousfilms.com/products/amiga-insights

Scroll down to the bottom-right. There's a video player for a trailer.

1. At its top-left, this graphic/font element is missing:

Error Console:

2. Full-screen button doesn't work. It will not go into full-screen mode.

[Moonchild]

I don't have time to investigate the first issue -- I don't get a font error at the very least.

2. Full-screen button doesn't work. It will not go into full-screen mode.

This is because it's an iframe and it isn't setting the allowFullscreen property, instead trying to set a (mobile-inspired) "permissions policy" with an arbitrary string -- we don't support that at this time. Basically "doing the same thing in an arbitrary other way" again which they do a lot these days...

See also: bug #1390801 - Implement feature-policy

[back2themoon]

Thanks for the info. No worries, I understand and don't expect solutions, immediate or otherwise. I just got the impression recently that it's best to keep reporting these, in an attempt to provide a clearer view of what is going "out there". Even though you and the rest of the team, probably already know the situation quite well.

I don't mean to paint a dark picture and this is probably nothing new or sensational, but it seems to me that in the last couple of years such minor issues (or less minor) keep cropping up at a steadily increasing, and quite fast rate.

In the earlier years, Facebook and a few big ones aside, it was usually just the odd, random and obscure website giving problems, often to be solved with a useragent override. I get the feeling this is not the case any more.

[Moonchild]

In the earlier years, Facebook and a few big ones aside, it was usually just the odd, random and obscure website giving problems, often to be solved with a useragent override. I get the feeling this is not the case any more.

No this isn't the case. There's been constant churn (and more is constantly being added to the already obscene collection of web standards and drafts, with everyone just pushing more new or rather reimagined ways to do things) and many sites have been problematic at one point or another. This is because we are pretty much forced to have a reactive implementation policy for web APIs. It's a constant balance between what is actually in use at scale, what is feasible to implement with a small team, what code is already there and/or what is maintainable, as well as in what way websites break down. "feature-policy" is a low priority thing because lack of it doesn't actually break things and primarily just causes some usability issues.
We've had much bigger issues with web compatibility than that, and those were impacting a lot of mainstream sites. Think of js modules, shadow dom, webcomponents, etc. Those were massive problems for our project, that couldn't be solved with overrides either. So no, this is not at all a more recent thing.

[vannilla]

Off-topic:
For completeness, the majority of websites out there actually use a framework like React, Vue, nuxt, etc., so when you see some widespread "breakage" it's usually because these frameworks added something from the neverending list of drafts Moonchild mentioned and websites updated their code to some newer version of their framework of choice.