This question is locked. New answers and comments are not allowed.
We've run into a problem with the batch editor functionality which we were able to reproduce on your website: http://demos.telerik.com/aspnet-mvc/grid/editingbatch
In the attached PDF shows the walkthrough of how to reproduce it. In the demo, using IE, I click on the word "Chai" to edit that field. Unfortunately, the input field does not have focus, so if I hit backspace right now, the browser will instead go to the previous page, since backspace is the shortcut for "go to previous page".
This is an issue because when doing batch editing, a user’s first action is very likely to be "delete the existing stuff so I can write something else in". Therefore, clicking on an input field and then hitting backspace is a common combination, and it is somewhat jarring to be redirected back to the previous page (when the user meant to delete the "i" in "Chai").
It only happens on Internet Explorer, and it only happens on the first click. Subsequent editing correctly gives focus to the input element. And Firefox always works, even on the first click.
p.s. Is it better to post bugs like this to the forum or directly to your public issue tracker?
In the attached PDF shows the walkthrough of how to reproduce it. In the demo, using IE, I click on the word "Chai" to edit that field. Unfortunately, the input field does not have focus, so if I hit backspace right now, the browser will instead go to the previous page, since backspace is the shortcut for "go to previous page".
This is an issue because when doing batch editing, a user’s first action is very likely to be "delete the existing stuff so I can write something else in". Therefore, clicking on an input field and then hitting backspace is a common combination, and it is somewhat jarring to be redirected back to the previous page (when the user meant to delete the "i" in "Chai").
It only happens on Internet Explorer, and it only happens on the first click. Subsequent editing correctly gives focus to the input element. And Firefox always works, even on the first click.
p.s. Is it better to post bugs like this to the forum or directly to your public issue tracker?