16 Jul 2008 12:27 PM #1
[2.1][FIXED] Ext.ux.Portal does not properly destroy Ext.ux.Portal.DropZone
a. Ext 2.1
c. Not OS Specific
d. IE6, Works fine in FF2
e. Simple setup... Tab panel with 2 items.
Ext.tree.TreePanel (containerScroll: true, activeTab)
What steps will reproduce the problem?
Show TreePanel (should show by default)
Attempt to drag a TreeNode
You will get an unspecified error in IE.
Can you provide a fix for this problem?
Problem arises because when the Portal is destroyed, it does not properly destroy the DropZone.
I have modified the example to include the panel's beforeDestroy method and the DropZone unreg method.
17 Jul 2008 2:17 PM #2
Looks good to me. Updated in SVN, thanks for the patch.
17 Jul 2008 3:00 PM #3
8 Apr 2009 6:43 AM #4
Sorry to resurrect this... but...
I was pulling out my hair, searching for a fix to the "Unspecified Error" we were getting when changing content in the Center-Region of our App.
The "StartPage" of the App is a Portal in the Center-Region which is then removed and replaced by a GridPanel in the center region.
The unspecified error popped up on resizing columns in this grid.
Diff'ing the Portal.txt against the Portal.js from SDK 2.2.1 i found out that the Line
Ext.dd.ScrollManager.unregister( this.portal.body );
is commented out in the current 2.2.1 SDK but has no comment in watrboys "Portal.txt"
and removeing the Comment made the column resize work again!
It seems to work fine so far and all, but i'd really appreciate if someone could clarify what the reason was to comment out that line in the 2.2.1 SDK.. I guess there was a good reason to do so?
8 Apr 2009 11:56 PM #5
Found a drawback in uncommenting the line... when reloading the Page with the Portal on it it says "Object expected" and complains about some Flyweights not being there... fixed it for now by surrounding the line with an try-catch but that aint a beautiful solution either....
16 Apr 2009 6:45 AM #6
If you're confident you have a new or bug that remains suggest you post a new thread. You haven't followed the directions when posting a new thread in bugs though, that is post working code that reproduces a problem. No one can fix a problem they can't reproduce themselves.
16 Apr 2009 7:04 AM #7
Ok then, ill throw together a minimal sample and post that as a new Bug.
I just thought it would be better to answer in a thread which describes almost the same problem.
16 Apr 2009 7:12 AM #8
As you've noticed the problem is the thread is taggged Fixed. Also you indicate "almost" same problem.
16 Apr 2009 7:50 AM #9
It's definitley in the same direction and the fix from watrboy partially corrects it... So i said "almost".
Btw i just got the sample ready and i am 100% sure now that this is rather a Problem in EXT than with my code.
Will post sample to Bugs now
16 Apr 2009 8:12 AM #10