I might've fixed this issue for the next upcoming update, but since I can't reproduce it myself I can't say for certain.
