Thanks for pointing out the error, I fixed it (quite late, I know).

I don't know the reasoning for the driver's behavior though, so your guess is as good as mine.