-
10 Oct 2012 2:29 AM #1
[4.1.2] Border layout: expanding collapsed region caused iframe reloading
[4.1.2] Border layout: expanding collapsed region caused iframe reloading
REQUIRED INFORMATION
Ext version tested:- Ext 4.1.2
- Chrome
- FireFox
- IE9
- Expanding a region of Border layout caused iframe reloading in the center region.
- Generally, it is a known issue when ifram reloads when moved into another DOM node, but, I think, it should not happen in this case.
- It doesn't happen on collapsing.
- collapseMode: "mini" for the region helps to avoid this issue.
- animCollapse: false doesn't help.
- Collapse the region
- Expand the region
- iframe does not reload
- iframe does reload
HELPFUL INFORMATIONCode:<html> <head> <title>Border iframe reloading</title> <link type="text/css" rel="stylesheet" href="../resources/css/ext-all.css" /> <script type="text/javascript" src="../ext-all-debug.js"></script> <script type="text/javascript"> Ext.onReady(function () { Ext.create("Ext.Viewport", { renderTo: Ext.getBody(), layout: "fit", items: [{ layout: "border", items: [{ width: 200, region: "west", collapsible: true, animCollapse: false, title: "East" }, { region: "center", contentEl: "iframe1", title: "Center" }] }] }); }); </script> </head> <body> <iframe id="iframe1" src="test.htm" class="x-hidden"></iframe> </body> </html>
Operating System:- Windows 7
-
10 Oct 2012 4:24 AM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,684
- Vote Rating
- 435
Thanks for the report.
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
-
24 Oct 2012 11:16 PM #3
Hi,
I have the same problem, is there any advance or a fixed version.
In any case, when could we have a release with this bug fixed?
-
25 Oct 2012 2:22 AM #4
Try
Code:Ext.override(Ext.layout.container.Border, { isValidParent: function() { return true; } });Search the forum: http://www.google.com/coop/cse?cx=01...%3Az7of1ufqccu
Read the docs too: http://extjs.com/deploy/dev/docs/
Scope: http://extjs.com/forum/showthread.ph...642#post257642
-
25 Oct 2012 6:58 AM #5
-
25 Oct 2012 7:50 AM #6
Just a workaround.
The fix is to write isValidParent to correctly determine whether the border child item really does need moving somewhere else within the container.
It's complicated by the extra Splitter Components being automagically inserted between Components, and the extra weirdness of placeholder Components which are what you see as the collapsed "representation". They are all in there, and isValidParent just doesn't do a good job right now.
I have the ticket open it will be fixed in 4.2Search the forum: http://www.google.com/coop/cse?cx=01...%3Az7of1ufqccu
Read the docs too: http://extjs.com/deploy/dev/docs/
Scope: http://extjs.com/forum/showthread.ph...642#post257642
-
25 Oct 2012 8:56 PM #7
-
25 Oct 2012 9:27 PM #8
4.1.3 is out. The code went into the 4.2 branch
Search the forum: http://www.google.com/coop/cse?cx=01...%3Az7of1ufqccu
Read the docs too: http://extjs.com/deploy/dev/docs/
Scope: http://extjs.com/forum/showthread.ph...642#post257642
-
25 Oct 2012 10:53 PM #9
Ok, thanks!
If you will have a chance, could you look at this, please?
http://www.sencha.com/forum/showthread.php?246801
Just I am interested in your opinion. I know you always have an independent opinion
(Apologize for a trick. Please just ignore if you wish.)
-
16 Apr 2013 8:04 AM #10
i think this problem still exists in IE 9. if I did panel.getLoader().load(), it throws a bunch of js errors in the URL provided. tested with other versions of IE and browsers, works fine.
Success! Looks like we've fixed this one. According to our records the fix was applied for
EXTJSIV-7470
in
4.2.0.179.


Reply With Quote