Can confirm on my end as well! Seems 18.1 has fixed this issue, although I couldn't find it in any release notes.