We just ran into something interesting where with the latest Telerik update the user ends up inserting two records (instead of one) when inserting a record.
User Behavior:
There is a popup with some prompts. Using only the keyboard the user types in the text boxes, hits tab, (repeat). When on the final text box, the user hits tab, this highlights the Insert button, then the user hits Enter.
As a result two records are inserted.
Note: this was only duplicated using IE8
System Behavior:
It appears that the Enter key submitted the page to insert a record, but it also submitted the page again as a response to having the Insert button activated.
As a result, the Insert record method was called twice by one Enter button press.
Work Around:
We found our popup had the following in the code behind's page load -
Page.Form.DefaultButton = btnSubmit.UniqueID;
We removed this and things are back to normal.
The Question:
We rolled back our Telerik dll to 2009q2 and did not have an issue with this popup, however the 2010Q1 version did. Any ideas as to what this might be in the 2010q1? We are scratching our heads over here.
Thanks!
Tim
User Behavior:
There is a popup with some prompts. Using only the keyboard the user types in the text boxes, hits tab, (repeat). When on the final text box, the user hits tab, this highlights the Insert button, then the user hits Enter.
As a result two records are inserted.
Note: this was only duplicated using IE8
System Behavior:
It appears that the Enter key submitted the page to insert a record, but it also submitted the page again as a response to having the Insert button activated.
As a result, the Insert record method was called twice by one Enter button press.
Work Around:
We found our popup had the following in the code behind's page load -
Page.Form.DefaultButton = btnSubmit.UniqueID;
We removed this and things are back to normal.
The Question:
We rolled back our Telerik dll to 2009q2 and did not have an issue with this popup, however the 2010Q1 version did. Any ideas as to what this might be in the 2010q1? We are scratching our heads over here.
Thanks!
Tim