Guys,
I've just migrated a solution to .NET4.0 to take advantage of the newer HTML5 support.
After some jigging around and updating, I finally got the input controls happy being rendered with type="email".
Problem is, this input control is returning NULL or blank when accessed through a button click event inside a RadAjaxPanel.
I have two other input tags, with type set to "text" and "password" right next to it, and they work just fine.
On further investigation, if call request.form[clientId] - the result is also null.
If I remove the RadAjaxPanel, the full postback works just fine, and the input field's value is read ok.
How weird is this? It sounds like the async postback is filtering input tags with type="email" as used in HTML5?
Any help appreciated.
Thanks.
I've just migrated a solution to .NET4.0 to take advantage of the newer HTML5 support.
After some jigging around and updating, I finally got the input controls happy being rendered with type="email".
Problem is, this input control is returning NULL or blank when accessed through a button click event inside a RadAjaxPanel.
I have two other input tags, with type set to "text" and "password" right next to it, and they work just fine.
On further investigation, if call request.form[clientId] - the result is also null.
If I remove the RadAjaxPanel, the full postback works just fine, and the input field's value is read ok.
How weird is this? It sounds like the async postback is filtering input tags with type="email" as used in HTML5?
Any help appreciated.
Thanks.
1 Answer, 1 is accepted
0
Hello Simon,
The HTML5 is still not fully supported by most of the browsers, and each of them has different problems. Could you explain what exact markup you are using and how it behaves in different browsers. If the problem is inside the RadTextBox we will fix it, but if it is browser problem and can be replicated using regular ASP TextBox or <input> element, there is no something that we can do about it.
Regards,
Vasil
Telerik
The HTML5 is still not fully supported by most of the browsers, and each of them has different problems. Could you explain what exact markup you are using and how it behaves in different browsers. If the problem is inside the RadTextBox we will fix it, but if it is browser problem and can be replicated using regular ASP TextBox or <input> element, there is no something that we can do about it.
Regards,
Vasil
Telerik
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to the blog feed now.