Hello I just experienced this bug using IBM's newest JRE v1.3.1. It does *not* happen so frequently with IBM's JRE as with Sun's, though, but still, it happens.(Again, dialogs are the problem)
Just wanted to point this out, so we know it doesn't only happen with Sun's java stuff. -- �yvind S.
