This bug still present in the regular version of mcpe v1.14.60.5
Yeah, It's also in the mcpe version in the latest version right now
This bug still present in the regular version of mcpe v1.14.60.5