Hi Tom,

Your app looks great!

Now, I’m depending on the LC browser widget where I set its HTML to handle the 
JavaScript YouTube API functions--so I can have interactivity with YouTube 
videos using LiveCode scripts. Are you doing something similar?

I’m trying to figure out why the a setup in Windows doesn’t work, while the 
same setup on Mac does.

I’m also wondering if LiveCode solved this issue when it built the YouTube 
widget—or is it that the widget just isn’t trying to do what I’m doing.

I think that having LC interactivity with YouTube videos is a great feature 
that can be added to the YT widget. There is an API for it, and the interactive 
use of YT videos in an application is squarely within Google’s terms of service.

Peter

> On May 27, 2026, at 2:38 PM, Tom Glod via use-livecode 
> <[email protected]> wrote:
> 
> Hey Peter, I am unable to dig into this, but I built a browser based
> youtube app a while back, and did not have any of these issues .... so here
> is the app, I hope it can help you.
> It works as expect on Windows. https://browserapps.io/YouTube-Time-Machine/
> 
> On Tue, May 26, 2026 at 3:07 AM Peter Bogdanoff via use-livecode <
> [email protected]> wrote:
> 
>> Hi LC people,
>> 
>> For my LC application "Music in the Air" I’m using the browser widget (of
>> LiveCode 10.0.0) to play YouTube videos in an iFrame following their API.
>> I’m also using JavaScript handlers to control the YT video player—play,
>> pause, currentTime, seek, etc. The works great on MacOS.
>> 
>> However, when doing the same thing in Windows 11, when the YouTube video
>> starts to load, the player shows an error:
>> 
>>        Error 153, Video player configuration error.
>> 
>> YouTube’s  iFrame Player API doc explains:
>> 
>>        Error 153 – The request does not include the HTTP Referer header
>> or equivalent API Client identification. See API Client Identity and
>> Credentials for more information.
>> 
>> That page:
>> 
>> https://developers.google.com/youtube/terms/required-minimum-functionality#embedded-player-api-client-identity
>> 
>> 
>> explains:
>> 
>>        "API Clients that use the YouTube embedded player (including the
>> YouTube IFrame Player API) must provide identification through the HTTP
>> Referer request header. In some environments, the browser will
>> automatically set HTTP Referer, and API Clients need only ensure they are
>> not setting the Referrer-Policy in a way that suppresses the Referer value.
>> YouTube recommends using strict-origin-when-cross-origin Referrer-Policy,
>> which is already the default in many browsers."
>> 
>> Now, I’m supposing that the MacOS LC browser widget of LiveCode 10 has the
>> HTTP Referer request header set, and the Windows widget does not.
>> 
>> Can that header be set in my HTML/JavaScript? And what would that header
>> say?
>> 
>> I also suppose that the YouTube widget that’s part of LiveCode 11 has this
>> taken care of. However that widget doesn’t have the interactive player
>> functionality that I need, and right now the LiveCode player control in LC
>> 11 doesn’t work reliably, and there are other issues with the player call
>> backs in versions of LC 10 beyond the first release that force me to use
>> ONLY 10.0.0.
>> 
>> Is there an updated LC 10 browser widget for Windows that has this fixed?
>> 
>> Any help with this would be greatly appreciated!
>> 
>> Peter Bogdanoff
>> ArtsInteractive
>> 
>> 
>> _______________________________________________
>> use-livecode mailing list
>> [email protected]
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
> _______________________________________________
> use-livecode mailing list
> [email protected]
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to