I don't think this is a bug. It's just one of the drawbacks of rapid
prototyping/development that hosted mode provides. You see, hosted
mode uses this custom browser (the GWT Shell) that is not really
running in a normal mode; it's drawing your html elements directly
from your Java code,
I found some related tickets some time ago:
* gwt ticket:
http://code.google.com/p/google-web-toolkit/issues/detail?id=283
* swt ticket: https://bugs.eclipse.org/bugs/show_bug.cgi?id=59506
* java ticket: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6587166
On Feb 18, 9:56 pm,
Thanks!
Is there a bug filed with Sun or Google that I can track?
El Mentecato Mayor wrote:
Yes, this is a known problem. Hosted mode doesn't support applets (not
running a real html/javascript page), so you'll have to test your
applet integration on web-mode only.
I do something like
Yes, this is a known problem. Hosted mode doesn't support applets (not
running a real html/javascript page), so you'll have to test your
applet integration on web-mode only.
I do something like this:
if (GWT.isScript()) { // running on web mode
applet = new AppletPanel();
}
else {
I'm writing a GWT app that embeds a Java applet (for legacy reasons).
Whenever I try to run it in Hosted Mode, the host browser crashes, so
I have to compile it and load it in a real browser, slowing down my
development process and preventing me from using the step-through
debugger.
Is this a
