@otagi Oh we actually fixed it after 2.3.3. Sorry. We don't want to push another update just for this one fix, but it will be resolved in the next update.