> > What problem is it you're trying to solve? That's going to dictate the > solution.
The problem is solved: not using the method construction: Document.get().isOrHasChild(element). Instead I use: Document.get().getDocumentElement().isOrHasChild(element) But, the outcome smells like a bug, so maybe somebody can try to reproduce this. If you can reproduce it, it's a bug, otherwise I might have to dig deeper and make an isolated test and hope I can still reproduce it. If so, I can drop the test here. Or maybe it's just some stupid coding mistake I overlook. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
