That is indeed a bug! I'm implementing the fix right now. The current patch in development is fairly substantial so it's taking a bit to complete. We'll put out an announcement when it goes live.
