then thats probably a bug/issue on the experimental branch, as this is not the case on the released version.
sounds like a regression, perhaps something thats still being worked on.
if your not a developer, really you should use the 1.0.12 branch as your base, experimental will have a number of 'oddities', its not supported/nor fully tested as its not meant for end-users.
Im also not sure of its state, and if its really ready for testing or not... it may be something are still 'works in progress'.
If your a developer, of course your help in fixing this kind of issues would be greatly appreciated - communicating via GitHub issues will help, so that you can attach the issue to your fixes when doing a pull request.
(also you can discuss potential fixed with Johannes in advance, check that he is not already doing something in this area)
Mod note: as this is a development release 'issue', Im going to move to developer category and adjust title.