Hi all,
As Thomas says, it's a known bug for which there has not been solution
for a long time (I had the same problem). The hack is simple but as
the GWT team doesn't know why this is happening (it shouldn't) they
have not solved it yet.
The bug doesn't appear in firefox, only in ie, but it's
On May 29, 11:26 am, jorge jorgelopezma...@googlemail.com wrote:
Hi all,
As Thomas says, it's a known bug for which there has not been solution
for a long time (I had the same problem). The hack is simple but as
the GWT team doesn't know why this is happening (it shouldn't) they
have not
just edit the compiled script, change
if (o.nodeType) {
to
if (o o.nodeType) {
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to
That just introduces more problems.
1) Not maintainable - you have to remember to change it every single time
you compile.
2) It's a hack. Without understanding the real cause, you are just asking
for more problems later on. The problem could resurface elsewhere you
won't know why you'll
On 28 mai, 14:57, Vitali Lovich vlov...@gmail.com wrote:
That just introduces more problems.
1) Not maintainable - you have to remember to change it every single time
you compile.
2) It's a hack. Without understanding the real cause, you are just asking
for more problems later on. The
When i run the debugger, everything runs fine. however, when I try
using ie itself I sometimes get.
540 function
com_google_gwt_dom_client_Element_is__Lcom_google_gwt_core_client_JavaScriptObject_2
(o){
541 if (o.nodeType) {
542 return o.nodeType == 1;
543 }
544 return false;
545 }
Oh ya, after this error happens, nothing is clickable anymore.
On Apr 1, 9:48 am, flyingb...@gmail.com flyingb...@gmail.com
wrote:
When i run the debugger, everything runs fine. however, when I try
using ie itself I sometimes get.
540 function
When the script debugor editor runs it shows this:
function com_google_gwt_event_shared_HandlerManager_
$fireEvent__Lcom_google_gwt_event_shared_HandlerManager_2Lcom_google_gwt_event_shared_GwtEvent_2
(this$static, event){
var oldSource;
if (event.com_google_gwt_event_shared_GwtEvent_dead) {
Not sure what you mean - what debugger? The proper way of debugging GWT is
to run it in hosted mode, where it's your Java code that's being executed.
On Wed, Apr 1, 2009 at 12:55 PM, flyingb...@gmail.com
flyingb...@gmail.comwrote:
When the script debugor editor runs it shows this:
function
But that does not show any errors at all. When I run the hosted mode
debugger no problems show up. It only happens when I am using IE. Does
not happen in the debug host mode thing. even though alert box says it
is internet explorer.
On Apr 1, 9:59 am, Vitali Lovich vlov...@gmail.com wrote:
The hosted mode browser is some hacked up version of IE6 AFAIK. I am going
to say that
even if you compile in DETAILED mode, trying to track down a problem in the
javascript code itself is pretty difficult - probably a waste of time.
Try putting logging statements in your code (either log to
I think my last msg didnt post. I think I figure out the problem. It
has to do with DialogBox.
I had old code that I wasn't using anymore. It should not do anything
though. I not sure why it is causing an error in the program. But it
is caused by the dialogbox i think
12 matches
Mail list logo
