> does this still happen on 42.1/42.2? On 42.1 it works ok. (In reply to Marcus R�ckert from comment #6) > does this still happen on 42.1/42.2?