This should be fixed with this ticket in v3.3.
↧
This should be fixed with this ticket in v3.3.