Closed IjzerenHein closed 8 years ago
I'm with @michaelobriena, please see my comment: https://github.com/Famous/famous/issues/673#issuecomment-89352486
I'll provide you with a test case which shows the problem in action.
Hi, I've created a demo for this, which demonstrates the problem: http://gloey.nl/apps/setContent/
To reproduce, press the "Trigger bug: Set Content, Hide and show after 2 secs" button. This button executes two actions at once:
sequenceFrom([])
.After 2 seconds, the surface is re-shown, and you would expect that the content that was set using 'setContent' be shown in the surface. But that is not the case and instead the content is shown that was last in the DOM.
Interesting note:
I tried reproducing this problem first with a RenderController, but was unable to. After some investigation I noticed that the RenderController still shows the content for at least 1 render-cycle after .hide({duration: 0})
was executed on the render-controller and thus causes this bug not to be triggered.
Thanks for the test case. This makes sense. @TheAlphaNerd This is mergable.
@michaelobriena which milestone?
Are we certain that the surface will be recalled successfully after preventing the initial recall?
On Wed, Apr 8, 2015 at 2:37 AM, Myles Borins notifications@github.com wrote:
@michaelobriena https://github.com/michaelobriena which milestone?
— Reply to this email directly or view it on GitHub https://github.com/Famous/famous/pull/674#issuecomment-90820521.
@michaelobriena can you close this?
Can you elaborate on this? Not sure the exact breaking condition.