We'll try to get this fixed in 6.18. Thank you for reporting it!