I think those variables at the top should be inside the controller.

Does Monaca compile my app to native code? Or JavaScript code? How does it work. I can’t find any documentation.

I have had to resort to:

theNavigator.popPage({
    callback: function(){
        theNavigator.replacePage('myPage', { animation : 'none' } );
    }
});

It works fine, but now the user can see the page change because I have some element using ng-if=“user is signed in”. What I’m looking for is the original page to be refreshed while the sign in page is being popped.

Why was the refresh option removed from popPape()?

I found this issue on Github: 1831

I don’t understand why refresh for popPage was removed. In my case, the user is on a page. They click the sign in button which pushes the sign in page. After signing in, the sign page is popped. Then I would like for the original page to be refreshed.

@Fran-Diox oh sorry! I’m too eager to learn about new features. I look forward to reading the blog post.

I noticed this in the patch notes:

core: Support for HTMLTemplateElement (<template>). The former <ons-template> is still supported for backward compatibility.

Can someone provide me with a better explanation of what this means?

I would greatly appreciate it. :)

@Fran-Diox @misterjunio

@Fran-Diox ahhh. I thought you guys already created the custom element and that I was missing something. Thanks for the tips! #2 looks promising.

Is there a way to combine ons-tabbar and segments? I would like for the tabbar to look exactly like the segments. I was looking at the Onsenui CSS documentation here, but I am still confused as to how to go about this. I could not find any examples of the segment component in use.

@munsterlander Okay, thanks. CSS is a big NO-NO for me hahaha. I will experiment with ons-card.

@Fran-Diox @misterjunio @munsterlander

What is the difference between ons-card and div?

Why should I use ons-card instead of div?