This is where Andy Clover’s notes are invaluable.
Now all we need to know is where we are in the document, and what our destination is. We know what we clicked on, and what that points to. If we didn't find a destination, give up and let the browser do Var allLinks = document.getElementsByTagName('a') Now loop all A tags until we find one with that name Links have a hash attribute that contains the # and the section that appears after it in the URL, so let’s now walk through all the links in the document and check whether their name attribute is equal to the hash part of the clicked-on link: // First strip off the hash (first character) setTimeout can be used to a similar effect when requestAnimationFrame is. For scrolling to a certain position in an exact amount of time, window.requestAnimationFrame can be put to use, calculating the appropriate current position each time. Now, we need to find the destination: the tag that corresponds to the part after the hash in our clicked-on link. To scroll to the bottom of the page, the y-position can be set to. Just to be paranoid, we also check that what we’ve got is an A tag, in case we’ve missed something: if (() != 'a') return The useful location object tells us about the URL of the document we’re looking at now, so try this: for (var i=0 i The answer to this problem is to scroll the user through the document to the linked location, like this. When they’re navigating through a long document, users often are confused or disoriented when they click a link that jumps to another location in that same document.Īre they on the same page, or a different page? Should they scroll more from here? What’s going on?
0 kommentar(er)
