Uncaught Cannot tween a null target. Draggable bug?

[Sahil 2,627 Likes (Superhero)]

I was going through documentation and tried Draggable library and found a possible bug? But seems impossible to stay undetected. I thought I should report it.

 

So if element passed to Draggable doesn't exist it throws error and javascript stops working as well. Are we suppose to make sure element exists and then create Draggable object?

See the Pen meyagj by Sahil89 (@Sahil89) on CodePen

[GreenSock 13,314 Likes (Superhero)]

Generally, yes, it's a bad idea to create a Draggable on an element that doesn't exist. However, I did add some code in the upcoming release that should alleviate this scenario where you pass in selector text that has no results. You can try it out with the [uncompressed] beta version: https://s3-us-west-2.amazonaws.com/s.cdpn.io/16327/Draggable-latest-beta.js

[Sahil 2,627 Likes (Superhero)]

Clicking on draggable element gives mouse position as zero. Or it depends on different libraries we use to detect click position? Like in this case it is jQuery.

 

See the Pen EVaqqZ by Sahil89 (@Sahil89) on CodePen

[Sahil 2,627 Likes (Superhero)]

While using static hitTest method, is there way to detect which element is on top? For example, return true only if first element is on top else false?

[GreenSock 13,314 Likes (Superhero)]

As for your pageX/pageY thing, that looks like a problem with jQuery and is completely unrelated to GreenSock code. You can tap into our code like this:

Draggable.create(".draggable", {
    onClick: function(e) {
      console.log("clicked at ", e.pageX, e.pageY);
    }
});

As for determining which element is on top, you could compare the zIndex of the elements. That's not something Draggable does for you in hitTest().