Thank you for the report. I was able to reproduce the issue in 4.16 and 4.17. However, it looks like this is fixed in 4.18 Preview. I hope this clarifies any concerns you might have. If there is anything else that I can help you with please let me know.