Skip to main content

Search and Top Navigation

#9387 closed bug (notabug)

Opened June 20, 2013 10:48AM UTC

Closed June 21, 2013 02:11PM UTC

Error: 'data(...)' is null or not an object

Reported by: tward Owned by: tward
Priority: minor Milestone: none
Component: ui.dialog Version: 1.10.3
Keywords: Cc:
Blocked by: Blocking:
Description

jQuery 1.10.3 Dialog issue with IE8

Line: 10

Error: 'data(...)' is null or not an object

Example:

http://jsfiddle.net/tward/qV3hY/

Clicking the "testing" link shows a dialog. Click anywhere in the overlay and you get the above message.

Others report it in Firefox as well, but I can't get it consistently there.

Attachments (0)
Change History (6)

Changed June 20, 2013 06:02PM UTC by tj.vantoll comment:1

owner: → tward
status: newpending

Hi tward,

Thanks for taking the time to contribute to the jQuery UI project. I'm seeing the error you're describing, but there's a lot going on in your test case so it's ascertain exactly what's happening. Would you mind reducing your test case to the absolute minimum amount of code needed that still shows the error?

The less JavaScript the better. Thanks!

Changed June 20, 2013 06:57PM UTC by tward comment:2

status: pendingnew

Replying to [comment:1 tj.vantoll]:

Hi tward, Thanks for taking the time to contribute to the jQuery UI project. I'm seeing the error you're describing, but there's a lot going on in your test case so it's ascertain exactly what's happening. Would you mind reducing your test case to the absolute minimum amount of code needed that still shows the error? The less JavaScript the better. Thanks!

I thought I had! I removed some more stuff that was not needed for the test case... Let me know if it is not enough.

Thanks.

Changed June 20, 2013 08:19PM UTC by tj.vantoll comment:3

status: newpending

Interestingly I no longer get an error in http://jsfiddle.net/tward/qV3hY/3/ but I do with http://jsfiddle.net/tward/qV3hY/2/. Are you seeing the same?

Changed June 21, 2013 10:34AM UTC by tward comment:4

status: pendingnew

Replying to [comment:3 tj.vantoll]:

Interestingly I no longer get an error in http://jsfiddle.net/tward/qV3hY/3/ but I do with http://jsfiddle.net/tward/qV3hY/2/. Are you seeing the same?

That is odd, but yes I am seeing the same thing. After more fiddling with it, it appears to be the following code that causes the problem:

   try
      {
       var LocatorDiv = document.getElementById('LocatorDiv');
       LocatorDiv.className="LocatorDiv";
      }
 catch(err)
      {
      }    

The only thing that changed when this started happening was when I upgraded the UI to 1.10.3.

Changed June 21, 2013 02:04PM UTC by tward comment:5

Replying to [comment:4 tward]:

Replying to [comment:3 tj.vantoll]: > Interestingly I no longer get an error in http://jsfiddle.net/tward/qV3hY/3/ but I do with http://jsfiddle.net/tward/qV3hY/2/. Are you seeing the same? That is odd, but yes I am seeing the same thing. After more fiddling with it, it appears to be the following code that causes the problem:
>    try
>       {
>        var LocatorDiv = document.getElementById('LocatorDiv');
>        LocatorDiv.className="LocatorDiv";
>       }
>  catch(err)
>       {
>       }    
> 
The only thing that changed when this started happening was when I upgraded the UI to 1.10.3.

I guess the LocatorDiv.className="LocatorDiv" is effectively removing "ui-dialog-content ui-widget-content" from the classNames, not sure why 1.10.3 has a problem with it, but I fixed it by not doing the above.

Guess it is not really a bug in jQuery UI, but a problem with what I was doing.

Changed June 21, 2013 02:11PM UTC by tj.vantoll comment:6

resolution: → notabug
status: newclosed

Ok. Internally the widget looks for those classes for determine whether clicks came from within the dialog.