I've got this strange problem with bootstrap, and I've searched around stack overflow as well as other sources to no avail. Basically, my 'Home' button on my nav is always pressed in, even when I am on the 'About' page or any other for that matter.
Here is an image of my nav so you can see what I am talking about.
http://i.imgur.com/wDcuEpm.png
I hope we solve this one guys!
You most likely have the active class set on the home element in a template. It should be set for the currently active page, not hardcoded to home. http://twitter.github.com/bootstrap/components.html#navbar
Related
I'm working on a project and using AOS animation but all div blocks that have an animation on them disappear whenever I refresh the page. I want to trigger a function whenever the page is refreshed so I can use the AOS.refresh(). Is there any way to do this in nuxt.js or maybe a way to go around this AOS bug?
UPDATE:
here's an example this is how the page looks before reloading:
then after reloading:
As you can see. the elements that still appear after the reloading are the ones without AOS animation.
Additionally, if you focus your eyes on the sidebar, notice I have a home page. this problem happens literally everywhere except the home page. When I go to the home page then I go back to other pages the problem basically disappears.
Not sure where is your bug coming from but so far, the homepage of the library achieves to have an animation on a page refresh. Maybe it is a lifecycle code issue at some point. Maybe post some for us to help you debug this one.
To my knowledge, there is no way of watching if your webpage is actually refreshed because there is nothing related to state before this. The only somehow useful thing that may be used sometime is this.$router.history._startLocation, which will give you the first path your webapp was loaded on.
Not sure if it may help you anyhow.
Also, you can maybe give a shot to this library in VueJS and wire it to Nuxt. Should behave pretty much the same.
I am using Vue 2.x.
There is a post page. When I click on a button in the post page, I go to the edit page. And when I click submit on the edit page, I used this.$route.replace(link_to_post_page) in order to remove the edit page from the history stack, and push the post page.
So now I have two of the same routes(the post page) in my history stack.
The problem is, when I click on the browser's back button, I go to the same page, that is, the post page. This is a very unnatural flow of pages for the user, and I want to fix it.
I have researched on ways to fix this for 6 hours, however I failed to find the solution.
My first try was to use Navigation Guards. But Navigation Guards only work when the route changes. In my case, the route does not change.
I also tried using window.history.onPopState event listener but failed with that too, because I could not manipulate the route when using window.history.onPopState.
I would really appreciate your help. Thanks.
P.S.
The most similar question on Stack Overflow is this vue-router: skip page when using browser back button but it does not answer my question at all. I have checked other questions but they also don't answer my question.
Why not going back in the history instead of pushing a new /edit route?
Steps
Routes stack
/post
['post']
-> Click on "edit" button
/edit
['post', 'edit']
-> this.$router.back()
/post
['post', 'edit']
The drawback of this is that the user still can manually go forward to the /edit page.
But if they go on another page, it will override the next steps (the /edit route above on the stack)
Ionic 2 allows a menu controller to show the standard hamburger nav menu toggle button in the nav bar. But by design, it only does this for the root page in the nav stack. The problem is that for an authenticated app, the login page needs to be the root page initially.
I can obviously set the root to the real root page after a successful login, but this causes two issues: 1) The nice page slide animation doesn't fire because it's not pushing a page onto the nav stack. 2) The menu hamburger isn't shown in that page even though it is the root.
This seems like a standard issue for most connected ionic apps, yet I can't find any complete examples. What's the recommended way to make this flow work (ideally without hacking past the built in menu management mechanism)?
UPDATE: The hamburger not showing (#2) was due to programmer error :( That's been resolved. Still looking for a solution to the animation.
this.nav.setRoot(Page, {}, {animate: true, direction: 'forward'});
Solution found enter link description here
After googling 'animate ionic setroot'
I have 2 pages in my Windows Phone 8 XAML app, "MainPage" and "Play".
I NavigateTo Play from MainPage, then hit the back button to return to MainPage.
Once I NavigateTo Play again, 2 things happen that I find confusing:
My constructor for Play is called again, yet the controls on the page still contain data from the last page visit.
Even though I see data in page members the data does not render on the screen.
There's something basic here I'm missing? How do I either get a completely new page; or re-render the previous instance?
Thanks
-John
You can use different class to hold your data, I think that is the problem. You can see this for more info.
I'm using a publishing web. I have two pages. The navigation is set to show pages.
It shows two menu items, for each page one item.
The problem:
When setting publishing page 1 as the welcomepage, this page is removed from the quicklaunch navigation.
Probable cause:
The PortalSitemap providers filters the welcomepages from quicklaunch. Probably because the web has the same url as the welcomepage?
Any thoughts about this and how to fix this by configuring the provider?
At this moment I added a (external) node...
Try to add page to navigation directly.
Site Settings => Navigation
you can use a little trick.
This happens because sharepoint removes the welcome page from the quicklaunch. But if you set the welcomepage with a different URL its appears.
for Ex: if you want the page "XPTO.aspx" to be your welcomepage, set it as "XPTO.aspx?".
this way the page will be set as welcomepage, and it will appear on quick launch .
this happens beacul sharepoint thinks that "xpto.aspx" and "xpto.aspx?" ate 2 different pages, but they are not.