This is a known issue. We are working on a fix, but UI time is currently at a premium, so I can't promise exactly when we'll have any specific issue addressed.