This issue is now occurring in the latest stable release (4.0.3). It wasn't a problem in 4.0.2. Possibly the fix for this was not included by mistake?
This issue is now occurring in the latest stable release (4.0.3). It wasn't a problem in 4.0.2. Possibly the fix for this was not included by mistake?