Comment 2 for bug 315903

I am also unable to repeat this problem on the current trunk. I followed the steps indicated in the bug report but I couldn't get anything.

Marco, can you check this bug against the current trunk (because I made a bunch of changes to event handling that might have eliminated your problem). If you can repeat the problem, can you please provide the exact set of steps that create it?

Thanks.