In August 2011 Microsoft released the "Microsoft .NET Framework 4 Reliability Update 1" (http://support.microsoft.com/kb/2533523) which amongst other things fixes two issues with the UpdatePanel control when using the new HTML5 input types such as "tel", "email" etc.
MicrosoftAjaxWebForms.js was updated as part of Reliability Update 1.
Unfortunately, because the Ajax Control Toolkit uses a forked version of several JavaScript files including MicrosoftAjaxWebForms.js, the version that is included with the Toolkit overrides the "standard" version of the .js file that includes the fix.
The result is that when you have an input control that uses one of the new HTML5 types e.g. <asp:TextBox ID="txtTelNo" type="tel" runat="server" /> and this is within an UpdatePanel, when you browse the page using recent versions of Chrome, Firefox or Safari (and probably other browsers) these fields do not postback.
The impact of this is that using the Toolkit prevents the HTML5 fixes in the Reliability Update 1 from working and HTML5 input controls do not work with browsers other an IE.
The sample code attached can be used to demonstrate the problem. In a brand new, empty web site project the code works with Chrome etc. but in a site that references the Toolkit, it does not.
Comments: And here are the fixed binaries of the May 2012 release - or you can just download the source, replace "PageRequestManager.js" with the attached one (just 2 lines of difference), and build it yourselves. Why is this assigned a "low" impact, when it is a completely feature breaking bug, and why it wasn't fixed in a whole 6 month period between releases !? This is the last time I'm doing this, from now on I'm using Juice UI instead.
MicrosoftAjaxWebForms.js was updated as part of Reliability Update 1.
Unfortunately, because the Ajax Control Toolkit uses a forked version of several JavaScript files including MicrosoftAjaxWebForms.js, the version that is included with the Toolkit overrides the "standard" version of the .js file that includes the fix.
The result is that when you have an input control that uses one of the new HTML5 types e.g. <asp:TextBox ID="txtTelNo" type="tel" runat="server" /> and this is within an UpdatePanel, when you browse the page using recent versions of Chrome, Firefox or Safari (and probably other browsers) these fields do not postback.
The impact of this is that using the Toolkit prevents the HTML5 fixes in the Reliability Update 1 from working and HTML5 input controls do not work with browsers other an IE.
The sample code attached can be used to demonstrate the problem. In a brand new, empty web site project the code works with Chrome etc. but in a site that references the Toolkit, it does not.
Comments: And here are the fixed binaries of the May 2012 release - or you can just download the source, replace "PageRequestManager.js" with the attached one (just 2 lines of difference), and build it yourselves. Why is this assigned a "low" impact, when it is a completely feature breaking bug, and why it wasn't fixed in a whole 6 month period between releases !? This is the last time I'm doing this, from now on I'm using Juice UI instead.