This has been fixed in v1.10.6. You must be experiencing some other issue. Can you provide a screenshot?