Hey Guys, I'm working a bug at the moment that has me pretty stumped, so I'm looking for some advice on how to debug this.
I work for Lincor Solutions (http://www.lincor.com) and we make a Bedside Entertainment system, primarily targeted at the healthcare market. It involves a custom PC with a touchscreen and our own linux based software stack based on FC5 and the latest FireFox2. I've setup a test system based on F9 and FF3b5 and it has the same problems. We use fullscreen browser based on C/C++ with gtk+-2 and GtkMozEmbed as our main UI. The problem occurs with a fresh login to gmail, it seems to be specifically related to their new UI. If i follow the link at the top of the page for the "Older version" this problem doesn't manifest itself. Once logged in, if I click on the compose link, pretty much everything loads with the exception of the message body window. Normally, when using my account, my signature would automatically be placed in the body window and I'd be able to enter my message above it. However, when I first go to the compose window, the body edit area never gets populated with the signature and never seems to become responsive to user input. The rest of the UI seems to be active and I can click away and come back. If it click on the Compose link a few times, I can see from my application log that the Gecko is trying to open about:blank and that's all. However, if I issue a refresh, then everything seems to start to work. So, I'm guessing that somethings going wrong with the javascript/ session but I've no idea how to debug that. So some suggestions are definitely most welcome. Kind Regards, -- Glen Gray [EMAIL PROTECTED] _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
