Hi Gal,
I’m not familiar with the framework you’re using, but the fact that the timeline is empty when you switch view is suspicious. Do you know if the views are help in the DOM at the same time (e.g. just hidden with CSS), or moved in and out when navigating?
Unfortunately when browsers move iframe DOM nodes they refresh their content upon insertion. With regular, remote sourced iframes this causes the content to be reloaded from the network. With sourceless, dynamic content iframes (which is what we use to sandbox embedded Tweets and timelines) the document that we’ve constructed gets obliterated, leaving behind an empty frame. From your description it sounds like this is what’s happening.
The only way to work around this would be to re-render the timeline when your view changes. It’s not ideal since you’ll be waiting for it to render each time, but unfortunately it’s only way to work with the browser behaviour. You may find the [node:25878] useful for this, maybe you can bind to show/hide events in the view framework to trigger twttr.widgets.createTimeline() on demand.
Hope that helps,
Ben