This is an unexpected behavior. The bug has been filed and will be fixed in the next version.
It has indeed been fixed in version 13.2.
thanks!