Hello
We are currently working with D&D framework and are observing an strange behaviour in IE8: when we add a webdatatree's nodes as source, once drag starts page is "frozed".
First I thought it could be related with the issue in FF already answered here http://ko.infragistics.com/community/forums/t/71736.aspx. But it was not.
Right now my observations are:
- It only happens in one of the webpages in the application (to big to upload)
- So far, observed only one difference between the page that works and the others: Nodes added as source have some attributes asigned like ontouchstart, ontouchend, etc... is this normal? Could it be the reason why it is not working? What should I look for in order to avoid this?
I will continue trying to isolate the problem but for the time being I would appreciate some hints in this matter as touchstart sounds strange in IE 8.
Thanks!
Hello rickycl,
Thank you for contacting Infragistics!
We received your support request concerning D&D framework, and this case has been assigned to me. Infragistcs is dedicated to helpping you solve this issue. Our team and I have done an inital review of your case.
I will create a sample to test this case. If you alread have a sample that I can use as a starting point that will help to resolve the case faster.
I will be updating you by the end of the day tomorrow of my progress.
If you have any questions, please let me know as well
Hi Vivian,
I haven't been able to isolate the problem, have you had any luck?
Is it normal that ontouchstart appears on the tree nodes when added as drag & drop source ? If it is not, under what circumstances is it normal? then may be we can shorten the list of things I can try in order to isolate the problem.
I have created a separate support case for this issue, as this may be related to an existing work item. I will be communicating with you through the support case.
If you have any questions, please let me know as well.
Thanks bro, im searching some how it...
Regards
Already answered on the support case but in case it helps anyone, removing the script described here (https://developer.mozilla.org/en/DOM/element.removeEventListener#Compatibility) and using the standard way to assign event handlers in javascript for ie8 solved the problem. Thanks!