We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testing out nuemark and having issues with the page router.
nuemark
For example:
A page with a nuemark tabs component http://localhost:8080/index.html
click a tab and the url changes to http://localhost:8080/index.html#tab-1
click link to a different page http://localhost:8080/example.html
click browser's back button and the URL is again http://localhost:8080/index.html#tab-1
however, the page content is still from the example.html
example.html
screencast:
The text was updated successfully, but these errors were encountered:
Ahh... good catch. I forgot to implement the collaboration between the tabs component and the page-router. Thanks!
Sorry, something went wrong.
Forgive me I might be off-topic, but I'm borrowing the topic of "page_router":
Is the page_router in site.yaml now deprecated in favor of router: true|false? I'm seeing only if (data.router) push('page_router')...
page_router
router: true|false
if (data.router) push('page_router')
But there are still two places that using page_router: true in create-www
page_router: true
@fritx yes, it has been replaced. See #113 with its closing commit be2f19a. Then this should be corrected in create and www
no_hotreload
router
No branches or pull requests
Testing out
nuemark
and having issues with the page router.For example:
A page with a nuemark tabs component
http://localhost:8080/index.html
click a tab and the url changes to
http://localhost:8080/index.html#tab-1
click link to a different page
http://localhost:8080/example.html
click browser's back button and the URL is again
http://localhost:8080/index.html#tab-1
however, the page content is still from the
example.html
screencast:
The text was updated successfully, but these errors were encountered: