Thanks for the report. I've seen that too. I've discussed it with Niklas a long time ago. We think this is a browser specific CSS related rendering bug that appears in the scenario you describe.
