I'm working on a site locally that has a fixed navbar with links that direct to on-page anchors. Everything was going fine, but then I realized at one point that upon clicking the link the page jumps to the anchor and then continues to jump back to the anchor every few seconds. I haven't put in any new javascript in, and I'm really at a loss for what could be causing the issue. Any ideas about what could be responsible?
Related
I've added a few anchor links on my angular project to help with page navigation and they seem to work.
However, when I'm testing them they only seem to work for one click; when I scroll back to the top of the page and click them again nothing happens.
The only way around it is to click to a separate page, come back and they work again.
Is there any way of fixing this so they allow multiple clicks without having to go back and forth between pages?
Thanks
I'm getting some weird behaviour with the Firefox back button after linking to id's in the same page. If I have some basic html like this:
link to header
... chunk of content ...
<h2 id="some_id">header</h2>
The first click on the link takes me to the header and the first click on the browser back button takes me back to the link. All good. But if I click the link again and then click the back button a second time the browser gets confused. The screen doesn't go back to the link. Worse if I scroll back then whenever the mouse hovers over the link (or even the address bar) the screen shoots back to the header without anything being clicked.
Here's the fun part. If I do click anywhere on the page after that second visit to the header then the back button works as normal. Also, if I open the dev tools overlay then the back button works as normal.
I've tried this with a totally stripped down file - just plain html with no scripts (even no css) - to remove any unseen errors.
Has anybody else run into this? Found a fix?
For a project a site is needed where when first loaded an animation appears that fades away and reveals the content of the site. I am fine with creating the animation and all. What I am not sure about is where to place it.
From a site ia point of view I see it like this. Either have the animation on the index page and once done remove that element with js or $ and reveal the index page. This means a reload will always show the animation again. This also means a click on the main logo that leads to the index page will also play the animation again. Something not really wanted or needed.
The only other option I see is having the animation on the index page and once done redirect to the home page where the site content is located. Like this a click on the logo can be set to either the home page or the index page. The info on the home page is also visible without watching the animation again since the home page has a separate nav link in the menu. Only if desired can the animation be watched again by clicking on the main logo.
From my perspective it will be the later. Though I ask you is this good practise? Is it OK to just have an animation on the index page and everything else on the home page?
I was thinking to either post this in https://ux.stackexchange.com/ or https://graphicdesign.stackexchange.com/ but I think this more concerns code architecture rather than design or ux because as mentioned the animation could also be loaded dynamically on the index page and once gone the content is shown on the index page. So you see I am not asking for opinion but rather for the right logic to tackle this task.
What method is best applied for this scenario? Would you consider having the animation on the index page and then redirect to the home page?
Linked
https://stackoverflow.com/questions/22090313/show-an-animation-before-show-my-index-html
https://stackoverflow.com/questions/503093/how-can-i-make-a-redirect-page-using-jquery
http://www.submittoday.com/splash_pages_and_search_engine_optimization.html
http://stackoverflow.com/a/22090389/1010918
https://stackoverflow.com/questions/30573395/page-loading-animation-method
https://stackoverflow.com/questions/1964839/jquery-please-wait-loading-animation
I am building a long Client List page for a site. There are links on other pages that are to jump to a specific category of client (Industry). Everything's working great except for when testing in Internet Explorer.
I have a link with the following URL:
/about-us/client-list/#environment-conservationJump
On the Client List page, I have the following anchor:
<a id="environment-conservationJump"> </a>
The first time I clicked on the link, it seemed to work, but now, after scrolling up and down the page a bit, if I refresh the page, it will jump to a different point in the page. Not always where another anchor exists, sometimes just part-way through one of the other lists.
In every other browser, everything is working great. I could just set the links to include a query string, and use jQuery to scroll down the page, but I'd prefer to not introduce another function to the page if I don't need to.
Has anyone run into this problem?
Whenever I click the "Home" option on my menu (left hand side, frames), a second copy of the menu page appears on the left side of the main window. The html of this link is identical to the other links, which work fine. As I'm just developing the site at the moment, the HTML of all the links is also identical. There is no code difference between this link and the others in any way, only the behavior.
The doubled copy of the menu is a phantom. It will not double itself again, and goes away when any other link, other than the home page, is navigated to. I'm currently in school and this is my first ground-up project, so I'm sure it's something stupid and simple.
Well Aarron, your problem is indeed quite obvious. After looking for hours, the solution the whole time is that your "Home" link is pointed at Index.aspx, which is the page with your frames, instead of Main.aspx. You were thinking of Index as your home page, which it is, but linking there in this context gave you frames within frames, instead of the default opening display page you were aiming for.