I'm wondering, i have this issue with focus change.
If i click anywhere inside the DataForm outside the input fields, focus goes to the first input field. It's pretty annoying if you try to hit some textbox, you miss it and then it ends up on a first field containg a dropdown, and then you accidentally change your dropdown selection:). Why is that happening and how to prevent it.
5 Answers, 1 is accepted
Thanks for reporting this issue. Although not a bug , still I agree this is an UX disadvantage and we definitely need to fix it . I am scheduling this for improvement.
One more time - thanks for the productive feedback ! I am updating your Telerik points.
I am afraid I can not offer a good workaround . A possible hack would be to set a null background for the elements in the form ( by editing the default template) , so that the "white" area becomes no hit testable.
the Telerik team
I have the same problem, is there a workaround for this issue?
I create a multi line textbox with height 80 in the AutoGeneratingField event. If I click on the white area (second to forth row) the focus goes to the first field of the data form.
We investigated the case and basically, we cannot change the behavior without introducing breaking changes (which is something we are definitely not fans of). Did you try the workaround suggested above ? Doesn't it meet your requirements ?
the Telerik team
Explore the entire Telerik portfolio by downloading Telerik DevCraft Ultimate.
I have a solution:
For more clarity, The memo field has a height of 80 (good for 4 lines).
Problem: If I click in the dataform on an empty memo on the second, third or fourth line the focus goes a way to the first control. If I click on the first line. The focus stays on the memo.
The proposed solution: ( is something probably not work with dynamic generated controls?)
A possible hack would be to set a null background for the elements in the form ( by editing the default template) , so that the "white" area becomes no hit testable.
This is the code I use:
The memo field:
The actual problem is that the MouseLeftButtonDown event bubbles down. The solution is to cancel this bubbling:
I hope it will help someone :)