Element.is() and Node.is() make no explicit guarantees about what happens if you give
them a null argument. It seems likely that the easiest solution to this problem would
simply be to be a bit more defensive, and explicitly allow null parameters (which of
course would cause them to return false). The cost shouldn't be terribly high, as you
normally only ever call these methods when you're unsure of a JSO's type, which isn't
all that often.

Code review: http://gwt-code-reviews.appspot.com/34801

(No comment was entered for this change.)

This issue was closed by r5332.

Any idea when this code fix will be out...?

With the code review link it looks that modified code I have it in the jar ... but 
still its throwing various native events null

 Issue 3716  has been merged into this issue.

 Issue 3663  has been merged into this issue.

@jgw: the issue seems to be marked for Milestone-1_6_1, but I'm guessing that's 
outdated since the fix seems to have just landed a few weeks ago. Marking as 
Milestone-NextRelease for now, feel free to remark if appropriate.

@jerome976: This fix is not included in GWT 1.6.4, so feel free to patch this in to 
see if it fixes the issue you've observed and let us know how it goes.

Actually, r5332 landed in releases/1.6 on May 11 (it was merged back up to trunk
later), so it will be in the 1.6 update.

The problem is: this issue is marked Fixed rather than FixedNotReleased, which also 
happens to make it "hidden" in the default search for issues (which only searches "Open 
Issues").

(No comment was entered for this change.)

sumitcha,

I patched up the latest fix to see that solves the reported problem it didn't. It 
looks like in Hosted mode I haven't seen any issue lately after the fix but in web 
mode the first time you try to show the DialogBox in my case it throws the Uncaught 
Javascript exception and hangs the system. When you refresh the browser, it doesn't 
throw me that exception at all and allows me to perform teh normal operation.

In my opinion fix is not stable.

@jerome: r5332 fixed the issues I was aware of, I as far as I can tell. If you're still having problems, please open 
a separate issue with the specific details of your problem, and code that reproduces it, if at all possible.

We are experiencing the same issues. Any idea when the 1.6 update will be 
available ? I can do some tests in development to see if the changes work, but I 
have to use an official downloaded version of GWT in production - so a new official 
GWT release would be great!

The patch seems to handle the problems we've seen in our application.

I'm hoping that this fix is in the 1.7 release.

This issue has been fixed in GWT 1.7.0 (see release notes):
http://code.google.com/webtoolkit/releases/release-notes-1.7.0.html

I upgraded the Google Eclipse plugin to 1.7 but that didn't immediately fix the
problem and left me scratching my head.  Turns out there was an additional manual
step (in project/window properties) needed to tell Eclipse to use 1.7 after the upgrade.

Of course, it makes perfect sense that you have to *use* the new code to get the fix
but I thought I'd post just to make sure no-one else hits the same snag.

(No comment was entered for this change.)

(No comment was entered for this change.)

jgw, 

Issue what I reported got solved as soon as I upgraded to GWT-1.7 it has passed all 
testing which we did with GWT-1.6 where we faced this issue.

Thanks you jgw sorry I don't know your name :( as well as sumitcha for following up.

Jerome.