Mar 23, 2010, 2:02 AM
[CLOSED] [1.0] Chrome refreshes the entire IFrame on pressing Enter inside TextFields
Please refer the attached image. This is a Panel. The Panel itself sits inside a Desktop Window created on the Desktop. Here's a quick Navigator:
Desktop -> DesktopWindow (Its Content P1.aspx is loaded inside an IFrame for the Window) -> P1.aspx contains the Panel whose image is attached.
I have added SpecialKey listeners for all controls here, TextFields, DateFields, Checkboxes etc. Everything works fine in IE & FF. But I face a very strange situation in Chrome.
I pull data on "Enter" key press for all controls from a WebService and populate the Grid. On pressing enter, the TextFields for eTripId, and ClientNumber work perfect.
But for all other controls, what happens is that Chrome issues the ajax WebService request, and then refreshes the entire IFrame itself with its content (p1.aspx). In other words, on pressing Enter, Chrome first issues the Ajax Request to the web service, and before waiting for its completion, refreshes the entire iframe content itself.
Because of a complex markup I am working with, I am not able to attach something reproducible. Hopefulle, the Ext.Net team can reproduce this. If not, I will try to assemble up a sample demo.
In the meanwhile, it's important to mention that using e.stopEvent() inside the SpecialKey listener for the offending TextFields, prevents Chrome from refreshing the window.
Desktop -> DesktopWindow (Its Content P1.aspx is loaded inside an IFrame for the Window) -> P1.aspx contains the Panel whose image is attached.
I have added SpecialKey listeners for all controls here, TextFields, DateFields, Checkboxes etc. Everything works fine in IE & FF. But I face a very strange situation in Chrome.
I pull data on "Enter" key press for all controls from a WebService and populate the Grid. On pressing enter, the TextFields for eTripId, and ClientNumber work perfect.
But for all other controls, what happens is that Chrome issues the ajax WebService request, and then refreshes the entire IFrame itself with its content (p1.aspx). In other words, on pressing Enter, Chrome first issues the Ajax Request to the web service, and before waiting for its completion, refreshes the entire iframe content itself.
Because of a complex markup I am working with, I am not able to attach something reproducible. Hopefulle, the Ext.Net team can reproduce this. If not, I will try to assemble up a sample demo.
In the meanwhile, it's important to mention that using e.stopEvent() inside the SpecialKey listener for the offending TextFields, prevents Chrome from refreshing the window.