Crash while executing endAnimatedJump method in a Flip view

Question

Hi, I experiencing a crash while executing endAnimatedJump method in a Flip view.

I have a flip view that is running an animation and the view change the callback for endAnimatedJump is executed in a page that was already unloaded. Is there any way to avoid the execution or to advise that DOM object doesn't exists anymore?

endAnimatedJump: function (oldCurr, newCurr) {
                    if (this._navigationAnimationRecord.oldCurrentPage) {
                        this._navigationAnimationRecord.oldCurrentPage.setElement(oldCurr.element, true);
                    } else {
                        oldCurr.element.parentNode.removeChild(oldCurr.element);
                    }
                    this._navigationAnimationRecord.newCurrentPage.setElement(newCurr.element, true);
                    this._navigationAnimationRecord = null;
                    this._ensureCentered();
                    this._itemSettledOn();

//The parentNode element is null here.

oldCurr.element.parentNode.removeChild(oldCurr.element); 

Answer 1

How about simply testing oldCurr.element.parentNode for null?

---

Jeff Sanders (MSFT)

Answer 2

I can't do that since the code is part of the WinJS library :(

Answer 3

What is the file and line number?  How can I reproduce this issue (pust a simple sample perhaps)?

---

Jeff Sanders (MSFT)

Answer 4

File: endAnimatedJump [ui.js] Line 12595

The issue is easy reproduced: You create a Filp view with a component and while it being animated you go to another page. What happens is that the call back endAnimatedJump is executed in the new page but trying to refer to the filp view component that was already unloaded. 

Answer 5

This solution may not be ideal but what we have done is called FlipView.next() until it reaches the end, then we call FlipView.previous() until it reaches the start in a loop. This seems to run quick enough that it doesn't look to bad.

We were informed that no more fixes will be available before launch, which includes a fix to the FlipView.currentPage setter.

This is the code which gets executed at our set interval:

if (!FlipView.next()) {
    for (var i = 0; i < FlipViewItemCount; i++) {
        FlipView.previous();
    }
}

Answer 6

Hi Ces,

There is a potential fix you can apply to override this problem.  You would need to override some code however.

What you would do is get a reference to your flip view (flip in the code below) and override the problem:

flip._pageManager.endAnimatedJump = function (oldCurr, newCurr) {
                        if (this._navigationAnimationRecord.oldCurrentPage) {
                            this._navigationAnimationRecord.oldCurrentPage.setElement(oldCurr.element, true);
                        } else {
                            if (oldCurr.element.parentNode) {
                                oldCurr.element.parentNode.removeChild(oldCurr.element);
                            }
                        }
                        this._navigationAnimationRecord.newCurrentPage.setElement(newCurr.element, true);
                        this._navigationAnimationRecord = null;
                        this._ensureCentered();
                        this._itemSettledOn();
                    };

-Jeff

---

Jeff Sanders (MSFT)

Answer 7

Thanks Jeff. I've gone ahead and used this workaround.

Answer 8

Unfortunatly, Jeff, flip._pageManager is undefined, but hopefully, flip.winControl._pageManager works. :)

Answer 9

Give it a shot.  This post is almost a year old and things have changed since the preview.  You can post your results here to help others!

-Jeff

---

Jeff Sanders (MSFT)