Thanks Chris, I am glad though, as it means it's a problem in code that I'm comfortable with and I've a working reference point.
I'm getting swamped with some other stuff at the moment so I probably won't get to finish this off today. But the plan is to strip it right back in my code and build it up again to see if I can isolate it. I'm sure I'll have a few questions about some of the API's that I didn't recognize, so you'll still be hearing from me. Regards, -- Glen Gray [EMAIL PROTECTED] On 2 May 2008, at 13:27, Christopher Blizzard wrote: > Glen Gray wrote: >> Ok, thanks to Chris's IRC prompting yesterday, I rebuilt xulrunner >> with --enable-tests (on F9, firefox's --enable-tests doesn't do >> anything for GtkMozEmbed testing, it has to be xulrunner). >> >> After a long re-build, I was able to test with TestGtkEmbed. I'm >> pleased to say that TestGtkEmbed DOESN'T exhibit the problem. This is >> good news for me as it means I've a reference implementation to >> compare API calls with and see if I'm doing anything stupid or >> missing >> anything in my initialization of the browser. >> >> I'll keep you posted as to any further progress I make with my own >> code base. >> -- > > I'm actually sad that it wasn't easy to reproduce in TestGtkEmbed. > Now > we can't help you track it down. :( > > --Chris > _______________________________________________ > dev-embedding mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-embedding _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
