I am using using telerik for some pages in my asp.net solution. On the start page, I have some buttons with the same design( they are ment to redirect to a aspx page) eg
<telerik:RadButton runat="server" ID="Button" NavigateUrl="Dest/Example.aspx"
Since latest chrome update (v 83), all requeste made are failing ( with status canceled).
The initiator seems to be
}else{if(!e||e=="_self"){window.location.href=h;
(telerik resource)
Does someone has an idea? Any help is appreciated.
So I am having the same issue and I believe this may need to be addressed at the browser level, but here is a workaround that is working for me until they fix it. I also tested that this is not limited to telerik, also asp buttons are broken. We have a lot of applications that have this type of code and it would be insane to add this code to all those spots. I guess we shall see if Chrome fixes it soon or not. I also sent in a "report a problem" on the about page in chrome and mentioned this.
Solution:
add OnClientClicking="OnClientClicking" to your button like this:
<telerik:RadButton runat="server" ID="Button" NavigateUrl="Dest/Example.aspx" OnClientClicking="OnClientClicking" />
and then in the javascript section add this: (taken and modified from teleriks radbutton demo code)
<script>
OnClientClicking = function (sender, args) {
var $ = $telerik.$;
if (sender.get_navigateUrl() && sender.get_buttonType() == Telerik.Web.UI.RadButtonType.LinkButton) {
var url = sender.get_navigateUrl()
//radopen(url, url);
window.location.href = url;
args.set_cancel(true);
}
};
</script>
Hope this helps!