I am having a problem with RadTreeView contextMenu clicks in Chrome 3. We have a production application that does not work anymore with chrome 3. This problem just happed this week, worked fine with earlier version of chrome. We have suggested that our users use chrome as it is very fast for ajax calls. Please help!
7 Answers, 1 is accepted
0
Hi WarrenH,
We tried to reproduce the reported issue on our TreeView / Context Menu online example, but to no avail. could you please provide details on what might be diferent in your case?
Thanks,
Paul
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
We tried to reproduce the reported issue on our TreeView / Context Menu online example, but to no avail. could you please provide details on what might be diferent in your case?
Thanks,
Paul
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
WarrenH
Top achievements
Rank 1
Rank 1
answered on 25 Sep 2009, 02:33 PM
Hi Paul,
2 differences, Our code base is ASP.NET Q2 2008 (I believe)... It was purchasd, worked fine sill works in Chrome 2. yet doesn't work in Chrome 3! Is this product still supported?! Where are getting lots of complaints from our users, as the Ajax is painfully slow in IE 8. Secondly, The treeview is nested inside a slider plane and a place inside a docking zone object, although I'm not sure that makes a difference.
2 differences, Our code base is ASP.NET Q2 2008 (I believe)... It was purchasd, worked fine sill works in Chrome 2. yet doesn't work in Chrome 3! Is this product still supported?! Where are getting lots of complaints from our users, as the Ajax is painfully slow in IE 8. Secondly, The treeview is nested inside a slider plane and a place inside a docking zone object, although I'm not sure that makes a difference.
0
Hi WarrenH,
The version of RadControls that you are using is almost an year old and Chrome 3 has just been recently released. It is highly possible that your version has issues with the latest version of the browser.
I strongly suggest you update to the latest version of Telerik.Web.UI and then test your page under Chrome 3 to verify that the issues still exist.
Best wishes,
Simon
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Best wishes,
Simon
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
WarrenH
Top achievements
Rank 1
Rank 1
answered on 26 Sep 2009, 08:56 PM
Hi Simon,
Have you dropped support for this? Can we expect a hotfix, this is really the preferred solution.
Are we simply too buy a new licence, 'redevelop' the application because it is slightly more than a year old? Doesn't seem like a very realistic solution on our end, the application is large in scope. Moreover, I've downloaded the trial version of the latest Telerik.Web.UI and I'm not sure how to change the asseblies to the new Telerik.Web.Ui dll. I dropped them into bin directory. The problem still persists.
Warren
0
Hi WarrenH,
It is still not clear from your post which is the exact version of the controls that you use. Do you use RadControls for ASP.NET 'Classic' (where the controls reside in separate assemblies, i.e. RadTreeView.Net2.dll) or RadControls for ASP.NET AJAX (all controls in one assembly - Telerik.Web.UI.dll)? Anyway, we tested the latest versions of both suites for the reported issue, but we are not able to reproduce it.
RadControls for ASP.NET 'Classic'
http://demos.telerik.com/aspnet-classic/TreeView/Examples/Functionality/ContextMenu/DefaultCS.aspx
RadControls for ASP.NET AJAX
http://demos.telerik.com/aspnet-ajax/treeview/examples/functionality/contextmenu/defaultcs.aspx
Regards,
Paul
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
It is still not clear from your post which is the exact version of the controls that you use. Do you use RadControls for ASP.NET 'Classic' (where the controls reside in separate assemblies, i.e. RadTreeView.Net2.dll) or RadControls for ASP.NET AJAX (all controls in one assembly - Telerik.Web.UI.dll)? Anyway, we tested the latest versions of both suites for the reported issue, but we are not able to reproduce it.
RadControls for ASP.NET 'Classic'
http://demos.telerik.com/aspnet-classic/TreeView/Examples/Functionality/ContextMenu/DefaultCS.aspx
RadControls for ASP.NET AJAX
http://demos.telerik.com/aspnet-ajax/treeview/examples/functionality/contextmenu/defaultcs.aspx
Regards,
Paul
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
WarrenH
Top achievements
Rank 1
Rank 1
answered on 28 Sep 2009, 01:04 PM
Hi Paul,
They are seperate assemblies in the bin directory and references like this in the aspx/master pages.
Perhaps the best course of action, is setting a up a support ticket. I'm not really sure how to do that, I can set up an ftp site so you can look at it, if you like .
They are seperate assemblies in the bin directory and references like this in the aspx/master pages.
<%@ Register Assembly="RadGrid.Net2" Namespace="Telerik.WebControls" TagPrefix="radG" %>
<%
@ Register Assembly="RadDock.Net2" Namespace="Telerik.WebControls" TagPrefix="radDK" %>
<%
@ Register Assembly="RadAjax.Net2" Namespace="Telerik.WebControls" TagPrefix="radA" %>
Perhaps the best course of action, is setting a up a support ticket. I'm not really sure how to do that, I can set up an ftp site so you can look at it, if you like .
Thanks,
Warren
0
Hello WarrenH,
Thanks for the clarification.
As you may have noticed from this example, the treeview context menu is working just fine under Chrome 3. The difference is that the online example uses the latest official versions of the 'Classic' controls. Obviously, we have fixed this issue in a later version and you will have to upgrade the controls in your application.
Greetings,
Paul
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Thanks for the clarification.
As you may have noticed from this example, the treeview context menu is working just fine under Chrome 3. The difference is that the online example uses the latest official versions of the 'Classic' controls. Obviously, we have fixed this issue in a later version and you will have to upgrade the controls in your application.
Greetings,
Paul
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.