The issue was acknowledged 7 months ago and claimed to have been fixed four months ago, but it is still present as can be seen here here and here