If you had already been to a page previously, and then navigated away from it, there was a flash of it's previous scroll position that showed. This ensures that only the view that is being animated in to view, is scrolled to the correct position, and the one leaving the view is left alone.
In _uihooks, sometimes the `next` argument is null, which means the new dquote> node should be appended to the parent. However, using jQuery
(`$(node).insertBefore(next)`), that's not possible, since jQuery
has no way of knowing what parent you mean.
Instead, this commit uses a standard DOM method,
`parent.insertBefore(node, next)`, which does the right thing --
it's what Blaze uses internally when no `insertElement` hook is
defined.
According to Ionic documentation:
"For iOS, tabs will appear at the bottom of the screen. For Android, tabs will be at the top of the screen, below the nav-bar."
http://ionicframework.com/docs/api/directive/ionTabs/
This change makes meteoric more consistent with Ionic making the UX closer to the native one.
This behavior can be prevented by passing any string to the style attribute, e.g. style="none", like in Ionic $ionicConfigProvider
http://ionicframework.com/docs/api/provider/$ionicConfigProvider/#tabs.style
I have a url that was fetched from collection data. I was rendering the template before the subscription was done and the template data was {url: null}.
Quick fix was to only render the template when the url existed but that cased a flicker when going though routes quickly.
This fix could have been done in an autorun but given that it is only called once this makes the most sense to me.
