This issue seems to be present in 0.11.9, too, but not in 0.11.8. The behaviour is identical to that disclosed in issue #707.