Hello ,
After testing this in 4.16 Preview 1, it seems that this issue is no longer occurring. While we don’t suggest active development in a Preview build, you may want to test this in the Preview to ensure that this issue is fixed for you.
Cheers!