Just confirming that this issue persists in Release 1.18. attached 4 screenshots with f3 on showing version.
Just confirming that this issue persists in Release 1.18. attached 4 screenshots with f3 on showing version.