Passing Cloudflare turnstyle challenge requires "Disable restrictions for this tab"?

[barbaz]

Using NoScript 13.6.17.901. The Cloudflare turnstile challenge on https://yamahamusicians.com/forum/viewtopic.php?t=18056 does not let me pass after setting ...yamahamusicians.com to Temp. TRUSTED, it just said my browser (the one I'm posting from) is unsupported. (That's incorrect per cloudflare's documentation Firefox 150 is well within the range of supported Firefox versions.)

I have ...cloudflare.com already set to Trusted, and there was nothing else in the NoScript popup to allow, nor anything else blocked listed in Netmon. Checked by temporarily setting each site listed in the NoScript popup to Custom, everything highlighted red was already allowed in my Trusted preset.

However, "Disable restrictions for this tab" in NoScript and this turnstile challenge immediately verified me.

What was NoScript blocking? How to find out & allow that without blanket-allowing like "Disable restrictions for this tab"? Or is this a NoScript bug?

(Have been told it's sometimes a bad idea to too much "pick at" problems with these types of verification systems, so hope I'm just missing something stupid )

[Giorgio Maone]

1. Is your TRUSTED preset allowing wasm and webgl?
2. Does your browser console show any "interesting" message?

[barbaz]

1. Is your TRUSTED preset allowing wasm and webgl?

wasm yes, webgl no. But wouldn't webgl would be highlighted in the Custom section in the NoScript popup if the site were using it? EDIT Or a NoScript placeholder, either in the bottom right of the page or somewhere else visible?

2. Does your browser console show any "interesting" message?

Umm... with Browser Console open, it just worked with Temp. Trusting ...yamahamusicians.com, as expected. No idea why having Browser Console open would make any difference??

[barbaz]

Is this related to https://github.com/hackademix/noscript/issues/549?

[Giorgio Maone]

Is this related to https://github.com/hackademix/noscript/issues/549?

Very likely. Can you confirm it's fixed in latest rc?