Also - when adding the Add On to chrome - this throws an error in contentScripts/login/opalHome.js:32 (clickLogin):
Refused to run the JavaScript URL because it violates the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules' http://localhost:* http://127.0.0.1:*". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
I am not sure what that even means, but i does not seem to have impact on functionality.
_Originally posted by @Nix-da in https://github.com/TUfast-TUD/TUfast_TUD/issues/131#issuecomment-1898394689_