This has been solved, note added to the documentation as this has consequences for users. Of course, the new implementation is better as it does what it says it does.