Jan 26, 2014, 7:49 PM
[CLOSED] Ext.net can crash IE 11 in rare case?
I have a reproducible test case within my application. I have tried to generate a stand-alone case but unfortunately, I am not able to. I was able however, to track down the cause (after much trial and error) but the solution is somewhere inside EXT.
The case is quite simple.
1. a page with a grid and a button.
2. button opens a modal window.
3. window accepts input data and submits to controller via directEvent.
the problem is that in the "Success" property of the button DirectEvent, we do two things
1. #{WindowA}.hide();
2. #{FormPanelA}.reset();
Now the FormPanelA is on the WindowA. It appears that order is critical here.
scenario #1:
If you hide the Window BEFORE you reset the form, it will crash IE when you try and open an accordion panel in the parent (after window closes)
scenario #2:
If you reset the FormPanelA BEFORE you hide the WindowA, then all is fine.
This ordering is important somehow and affects IE since it will crash every time in my application but works fine if the ordering is as in scenario #2.
Now I know I have no standalone case but this is important. I am happy to do a quick WebEx and show the problem. I am not sure how to get it to crash in a standalone case though but I am open to suggestions to try if someone can figure it out and suggest something.
Ext 1.7
IE 11
BTW, Chrome works just fine.
Thanks,
/Z.
The case is quite simple.
1. a page with a grid and a button.
2. button opens a modal window.
3. window accepts input data and submits to controller via directEvent.
the problem is that in the "Success" property of the button DirectEvent, we do two things
1. #{WindowA}.hide();
2. #{FormPanelA}.reset();
Now the FormPanelA is on the WindowA. It appears that order is critical here.
scenario #1:
If you hide the Window BEFORE you reset the form, it will crash IE when you try and open an accordion panel in the parent (after window closes)
scenario #2:
If you reset the FormPanelA BEFORE you hide the WindowA, then all is fine.
This ordering is important somehow and affects IE since it will crash every time in my application but works fine if the ordering is as in scenario #2.
Now I know I have no standalone case but this is important. I am happy to do a quick WebEx and show the problem. I am not sure how to get it to crash in a standalone case though but I am open to suggestions to try if someone can figure it out and suggest something.
Ext 1.7
IE 11
BTW, Chrome works just fine.
Thanks,
/Z.
Last edited by Daniil; Feb 07, 2014 at 6:58 AM.
Reason: [CLOSED]