no local userscripts will run

[paulwratt]

none of my local userscripts will run after the last update (yesterday). They are all in the list, and it says they are all enabled, but disable/re-enable and a page reload does nothing.

although they all have remote locations (homepage), they were all saved and edited locally (if that makes a difference)

EDIT:
I thought I'd check Convert CDATA sections into a browser compatible format is set, but eslint is showing null - Parsing error: unexpected token <. here is one of the pieces of code:

    pwt_gmailCSS=(<><![CDATA[
body {
  background-color: #121212 !important;
  background-size: cover !important;
  background-attachment: fixed !important;
}
table.h tr {
  background-color: white !important;
}
]]></>).toString();

TamperMonkey:
4.18.1 (2022-11-13)
Browser: (from the about box)
Version 92.0.4515.98 (Official Build) Built on Raspbian , running on Raspbian 10 (32-bit)
OS:
Raspbian 10 (32-bit) Buster (up-to-date)

here is the head of one that was working fine up until Yesterday (I rebooted yesterday), before Tampermonkey update

// ==UserScript==
// @name         Multi-select Gmail HTML
// @namespace    paulwratt.gmail
// @version      1.10.7
// @description  add the missing "select all" checkbox, and full labels, for the HTML (fast) version of Gmail
// @author       paul.wratt@gmail.com
// @icon         data:image/gif;base64,{ ** let me know if you need this ** }
// @homepage     https://paulwratt.github.io/gmail-html-pwtools/
// @include      https://mail.google.com/mail/u/*/h/*
// @run-at       document-end
// @grant        GM_addStyle
// ==/UserScript==

[paulwratt]

They just started working ... ???

nope stopped again ..

[derjanb]

Please check whether this solves the issue.

[paulwratt]

OK, I just used the second method mentioned in that Issue link (disable, quit, start, re-enable), and that seems to have "fixed the issue" (they all seem to be functioning correctly, and without fail).

If nothing else changes in the next 2 hours I'll close this ..

BTW can we get any comment on "why"? Hmm.. I see Chrome is to blame, but this Chrome has not been updated since before TamperMonkey was installed, maybe once about 9/10 months ago ..

[derjanb]

Please see #1617 (comment)

[paulwratt]

nup its broken again

[paulwratt]

and now the above fix does not work either ..

[derjanb]

nup its broken again

What changed? Tampermonkey was updated? Chrome was updated? If so, what are the version numbers?

[derjanb]

Please try the BETA version and re-open if the issues still happens. https://chrome.google.com/webstore/detail/tampermonkey-beta/gcalenpjmijncebpfijmoaglllgpjagf