I switched to the stable version of 2.5.1 and it seems this issue is not having this bug. Not sure why.