Current workaround is to deactivate them manually in code in the `afterInit()` method.
Current workaround is to deactivate them manually in code in the
afterInit()method.