Martin Auswöger

> Should I open an issue in Improvements/Feature No, this one is fine.

I was also not able to reproduce that, @aznoqmous can you give more detailed instructions on how this can happen? What browser are you using?

I was only able to reproduce this in Chrome on Windows. So maybe this is a Chrome-Windows bug.

In Chrome 95 on Windows everything still works correctly. So it seems this bug was introduced with Chrome 96 on Windows, and it therefore should be reported to Chrome.

> and it therefore should be reported to Chrome. Did anyone do that? Because if Chrome fixes it, we don’t need a fix in Contao itself and can close this...

Maybe the correct text would be `Do not call the constructor from an inherited class; decorate the "contao.security.token_checker" service instead and redirect the public methods to the inner service` or...

That would be valid for all services, so I’d only do this if decorating this service is common or an explicit extension point for us.

Is this issue still present or was it maybe fixed by #5060 ?

Does it appear with the debug mode as well as without? Does it make a difference if you clear the cache (`rm -rf var/cache/`)?

Should be fixed by #5163