Hi all,
Is there a way to prevent a WebDataTree scrolling back to the top when you check a node? I have the WebDataTree inside an ASP.NET UpdatePanel that is causing the issue. This occurs if the UpdatePanel is automatically updated or updated manuall with UpdatePanel.Update().
WebDataTree Properties:
AutoPostBackFlags CheckBoxSelectionChanged = OnEnableAJAX = TrueEnablerConnectorLines = TrueSelectionType = Single
Any ideas?
Thanks,
Andez
Hi Andez,
Are you saying that the tree itself is scrolling to the top when you check a node? Or is the page scrolling? If you can attach a sample, it would help to look at.
thanks,
David
David,
It is the WebDataTree that scrolls to the top. My example has 3 trees in it. One in UpdatePanel, one in WARP, and one in the Page. In my main application, I have the WebDataTree in an UpdatePanel.
To recreate, expand the nodes in any of the trees to make the scrollbar appear. Then click on the node at the bottom of the tree. When you click it it will scroll back to the top.
I've probably missed something but the UpdatePanel and the tree in the page scroll back to the top. The WARP one just disappears when you click on a node.
Cheers
Andez,
You shouldn't use the WebDataTree inside of a WARP. The WebDataTree is based on our Akido framework which uses Microsoft AJAX extensions. The WARP implements its own AJAX functionality, which can interfere. You should use an update panel.
My next quesiton is what build you are using. In this forum, http://forums.infragistics.com/forums/t/26932.aspx, someone was experiencing a similar issue. There was an internal bug logged for this case. The bug should be resolved in this month's service release. When I tried replicating your scenario in the latest build available to me, I couldn't reproduce it.
regards,
We don't use the WebDataTree in the WARP - we are using the UpdatePanel. The sample I attached was for experimentation.
We are currently on build 9.1.20091.2055. As far as I know this is the latest release.
I rechecked this out this morning using your sample. I was able to reproduce the issue with both build 2055 and 2061. I have submitted a bug, # 19308. What I suggest doing is contacting developer support and give them that number so that the bug can be marked public and your case attached to it. I will let our manager know and do the best we can to resolve this bug and have it in this upcoming Service Release, but with it shipping at the end of the month, it may or may not make it in. Thanks for bringing this issue to our attention.
Cheers Dave.
Is that under Support Requests link on My IG?