InformAction Forums

Most likely this bug - fixed in latest builds.

13.4.918 has the onboarding hooks.

Thank you for testing, please check 917

Please check 916, thank you (no startup hooks yet for onboarding, but I should have tentatively fixed a potential race condition which might have been the root cause of the inconsistencies you've noticed).

13.4.914 Uncaught TypeError: can't access property "addEventListener", document.querySelector(...) is null <anonymous> moz-extension://7c7f8afb-9c39-4b62-aad9-637a830738bc/ui/behavior.js:93 <anonymous> moz-extension://7c7f8afb-9c39-4b62-aad9-637a830738bc/ui/behavior.js:125 behavior.js:93:...

Probably the bug I've just fixed in 13.4.914 (missing UI synchronization step).

We were under a DOS attack from a bunch of Singapore IPs.

I've blocked them at the firewall level.

Please check latest development build:

v 13.0.8.903
============================================================
x [UX] Increase contrast for non-HTTPS site labels in dark
mode (thanks Soothsayer for reporting)

Thank you, it should be fixed in latest development build:

v 13.0.8.902
============================================================
x Fix CSS error causing permanent permissions switch to be
shown in every context (thanks barbaz for reporting)

It's https://github.com/hackademix/noscript/issues/444 and it's fixed in latest develpment version.

1. Are you setting those permissions while in Incognito mode?
2. Have you got any "Cleaning" software which claims to scrub your browser data?

barbaz wrote: ↑Tue May 20, 2025 12:19 am Is there any possibility this is related to when a site registers a ServiceWorker?

Good call.

It's tracked as issue #444, and should be fixed in 13.0.6.902.

What if we remove the technical stuff and just try to convey the basic information? "Automatically trust sites loaded as the top level document" Speaking about "current session" is technically correct, but kinda moot, because as long as the option is enabled this keeps happening ...

I'll try to better detail the reasoning behind my "Automatically grant TRUSTED capabilities to the top-level document's origin" proposal: 1. We don't apply neither the "TRUSTED" nor the "Temp. TRUSTED" presets anymore: instead we create and apply a CUSTOM capabilities s...

OK, after re-reading the whole thread, and taking in account issue 417's resolution, I'd settle with
"Automatically grant TRUSTED capabilities to the top-level document's origin'.

WDYT?