Thank you for your report. This is indeed bug which was created in version 2.5.9. It will be fixed with version 2.6.0

We will review this idea.