Error When Opening YouTube

[camoman1234567]

Is there an existing issue for this?

• I have searched the existing issues

Type

User Script

Web Browser

Brave

URL

youtube.com

What happened?

Every time I open youtube I get this error:

[Magic Userscript+] (make) Failed to set the 'innerHTML' property on 'Element': This document requires 'TrustedHTML' assignment.

It just started happening about an hour ago.

Steps To Reproduce

1. Have Magic Userscript+ : Show Site All UserJS enabled in tampermonkey
2. Open youtube

[magicoflolis]

I see the problem, I will fix this in the next update

[magicoflolis]

Fixed as of v7.1.1, the Trusted Types API is the issue.

The trustedTypes.createPolicy() function is already added to the script to bypass this, however it looks like on youtube.com with the Brave browser it needs to be injected sooner.

window.trustedTypes.createPolicy('default', {
  createHTML: (string) => string
});

If this does not fix your issue create a new issue along with any additional UserScripts or WebExtensions you have installed for youtube.

[neoOpus]

This is happening again in all google services

[jfkruuse]

Yeah showing up in more and more places now

[magicoflolis]

From my understanding this was due to multiple cases of my use of innerHTML and the webpages use of TrustedPolicy. This issue comes up on Chromium (Chrome, Edge, Opera) but not Firefox.

I have a permanent fix for TrustedPolicy but the issues on YouTube specifically still remain due to another reason.

This is due to YouTube's ES5 custom element polyfill wrapper, custom-elements-es5-adapter.js, and my recent changes. YouTube loads a polyfill for older browser which Custom Elements are not supported. The script does inject on the first page load but won't inject again when navigating, e.g. going from video to video, or load SVGElements.

Over the past year I have been slowly rewriting this script to use Custom Elements, I did this to improve working with the script and it improved many other things that I won't get into in depth here.

I did not predict a site would break the default behavior of window.customElements regardless of the browser environment.

Lastly future updates may be slow as this is a side project. I work in a office now and do not have much free time to hammer things out like I used to.

I haven't given up, I just do not have a permanent solution for now.