[DavidBachmannParticipant]

This is not some exotic feature request. This is default browser behavior that is commonly used that breaks the component. If the component cannot handle the drop, it should reject it. This would at least communicate to the user that this does not work. It should not look as if worked when it didn’t.

[DavidBachmannParticipant]

It is not a problem to check that, if the behavior was documented anywhere. I also think it should not be a problem to check if the _hittestrow method returns undefined, since it is explicitly programmed to return undefined, and get rid of this bug, rather than force your customers to work around it.

Best Regards,
David Bachmann

[DavidBachmannParticipant]

Hello Dimitar,

so if I want to collapse specific elements, other than root, I have to scan through the getItems Array and find the item matching the one I want to collapse?

Also, the jsfiddle has the same problem as every jsfiddle in the “API Reference” section of your Web Demo. You have to enable untrusted sources in the browser, because jsfiddle uses HTTPS and your scripts are delivered using HTTP. You can do this using a shild icon in the address bar in chrome.

Regards,
David Bachmann

[DavidBachmannParticipant]

Close enough, thank you!

[Author]

Posts