This issue was introduced when bug #326678 was fixed. We could revert the patch and reintroduce the old behaviour, or come up with a tradeoff that improve both issues. Not quite sure how to do the latter, so I am unsure how this should be handled. Happy hacking, -- Petter Reinholdtsen