By now, [data-load] is performed when the page (main or not) is requested as a web page. When lading the page, all the data-load are processed, but that's the end of the flow.
That leads to misunderstanding, since when a developer uses data-load but he/she wants to navigate forward/backward, the data-load inner pages are not requested by the router. (As it would be if the inner pages where requested from the ir.router(name).configure(()=>{ir.load(...)})
So take one implementation decision:
either leave it as is (an easy to use and understand property with limited features)
or implement code to add data-load pages to routers, example data-load="..." data-router="..." (this would be the same as ir.router.addPage(url,container);
By now, [data-load] is performed when the page (main or not) is requested as a web page. When lading the page, all the data-load are processed, but that's the end of the flow.
That leads to misunderstanding, since when a developer uses data-load but he/she wants to navigate forward/backward, the data-load inner pages are not requested by the router. (As it would be if the inner pages where requested from the ir.router(name).configure(()=>{ir.load(...)})
So take one implementation decision: