Having some strange issues in FF creep up. No probs in IE right now.
Seems the input text fields are not losing focus after I tab off of them or click on some other control.
When I click on a submit button or drop a telerik drop down menu, that action seems to force user interaction with the inputs since the input never lost focus; if that makes any sense...
When I click my submit button it's like the user is clicking the submit and also typing in the current text value into the telerik input field at the same time. The text box proceeds to show a drop down of previous user inputs into that field as if the user jsut typed into it even though the only action is clicking the submit (or whatever the case may be).
I think if the text boxes just lost focus like they should I would avoid this issue.
Anyone else having input manager issues in Firefox?
I've used the input manager in FF before without any problems...
Seems the input text fields are not losing focus after I tab off of them or click on some other control.
When I click on a submit button or drop a telerik drop down menu, that action seems to force user interaction with the inputs since the input never lost focus; if that makes any sense...
When I click my submit button it's like the user is clicking the submit and also typing in the current text value into the telerik input field at the same time. The text box proceeds to show a drop down of previous user inputs into that field as if the user jsut typed into it even though the only action is clicking the submit (or whatever the case may be).
I think if the text boxes just lost focus like they should I would avoid this issue.
Anyone else having input manager issues in Firefox?
I've used the input manager in FF before without any problems...
2 Answers, 1 is accepted
0
Hi Matt,
Based on this information, it is hard to determine what is causing the issue in Firefox.
If the issue persists, you can open a formal support ticket, and supply a small project, demonstrating your logic, for additional review.
Sincerely yours,
Pavlina
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Based on this information, it is hard to determine what is causing the issue in Firefox.
If the issue persists, you can open a formal support ticket, and supply a small project, demonstrating your logic, for additional review.
Sincerely yours,
Pavlina
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
Ellison Bayan
Top achievements
Rank 1
Rank 1
answered on 31 Oct 2009, 09:39 PM
Hi. I'm new and signed up here just for this question (I don't even know what "telerik" is, so please forgive my intrusion). I think I'm having the same problem, and this is the only relevant result when I Googled "input not losing focus".
Something that might be significant is that the inputs that aren't losing focus are inside an iframe, and the bug only appears after dynamically creating and appending new rows to the table that contains the inputs. The containing page has additional inputs, and what's interesting is that clicking on those inputs in the containing page puts the blinking cursor in the input, but there is STILL the blinking cursor in the input in the iframe, so it looks like two inputs have focus at the same time (one inside the iframe and one in the page containing that iframe).
Additionally, clicking in any of the containing page's inputs will make the iframe's inputs lose focus correctly, or even make this bug not happen at all if one of the outer inputs are clicked before clicking any of the inner inputs. The same goes for clicking to another browser tab, clicking outside of the browser window, and putting a javascript alert somewhere between the point at which the function to create the row is called and actually clicking on an input.
If any progress has been made on this issue, or if there's a formal ticket somewhere specifically for this, please point me in that direction. Thank you.
Something that might be significant is that the inputs that aren't losing focus are inside an iframe, and the bug only appears after dynamically creating and appending new rows to the table that contains the inputs. The containing page has additional inputs, and what's interesting is that clicking on those inputs in the containing page puts the blinking cursor in the input, but there is STILL the blinking cursor in the input in the iframe, so it looks like two inputs have focus at the same time (one inside the iframe and one in the page containing that iframe).
Additionally, clicking in any of the containing page's inputs will make the iframe's inputs lose focus correctly, or even make this bug not happen at all if one of the outer inputs are clicked before clicking any of the inner inputs. The same goes for clicking to another browser tab, clicking outside of the browser window, and putting a javascript alert somewhere between the point at which the function to create the row is called and actually clicking on an input.
If any progress has been made on this issue, or if there's a formal ticket somewhere specifically for this, please point me in that direction. Thank you.