[Solved] How to use navigation inside nested routes with routable modals

Questions
1

Use case:
Page L do the user login and navigates to Page A.
Page A invokes a popup with Page PA.
Page PA navigates inside the popup to Page PB.

1st try:
Opening the popup manually. Works fine, except for a navigational bug: when in Page PB, the browser back button (or Android back button) backs to Page PA only if the popup view have pushState="true". And, when in Page PA, back button navigates the main page for the Page L (and leave the popup open).

2nd try:
Tried to create the following routes (and removed any manual popup behavior, as open, close, etc.):

{
    path: "/root/pageA",
	isSecure: true,
	component: APageComponent,
	routes:
		[
			{
				path: "pagePA",
				popup:
				{
					isSecure: true,
					component: APopupComponent,
				}
			},

			{
				path: "pagePB/:parameter",
				popup:
				{
					isSecure: true,
					component: APageComponent,
				}
			},
		]
},

Works wonderfully and magicaly, except I can’t navigate to Page PB =\
console.info shows me the router was activated, but nothing happens.

3rd try:
Page PB now is a <f7-popup><f7-view><f7-page>... instead of a <f7-page>.

Now PagePB opens a new popup over the Page PA popup (and the Page PB back button does nothing).

4th try:
With Page PB back to a <f7-page> component, tried this nested-nested-route:

	{
		path: "/commerces/commerce-management",
		isSecure: true,
		component: CommerceManagementPage,
		routes:
			[
				{
					path: "create-new-commerce",
					popup:
					{
						isSecure: true,
						component: CreateNewCommercePage,
						routes:
							[
								{
									path: "add-new-commerce/:pageId",
									popup:
									{
										isSecure: true,
										component: AddNewCommercePage,
									}
								},
							]
					}
				},
			]
	},

Now Page PB closes the Page PA popup (console says I’m going to a 404 (there’s a path: "(.*)", catcher))

How can I make the popup navigable to Page PB? =(

2

Solved (with just one minor “I don’t like it” detail):

Page PA has no url in <f7-view>.

The Page PB has an url of /folder/pageA/pagePA/pagePB/parameter (that’s the part I don’t like, because Page PB isn’t really a child of Page PA.

The route:

{
	path: "/folder/pageA",
	isSecure: true,
	component: APageComponent,
	routes:
		[
			{
				path: "pagePA",
				popup:
				{
					isSecure: true,
					component: APopupComponent,
				},
				routes:
					[
						{
							path: "pagePB/:pageId",
							isSecure: true,
							component: APageComponent,
						},
					]
			},
		]
},

I’m too tired (it’s 3AM here) to test it further, but I guess it’s this =P