Same behaviour here, it took me very long to find out that this is a bug. Fortunately I could bypass this with a workaround.