You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a traditional pageload, the page will be scrolled to the top. This is especially important when navigating from a long page to another page - being in the middle of the new page is disorienting. A short-term solution would be to use the following after a DOM write:
I think this is valid and I don't see it solved in this library. Exact behaviour should be discussed though. There are lot of exceptions to this, like:
going back
opening/closing modals
replacing with content which differs in minor thing only
Ajaxcom solves some unintuitive default browser behaviour regarding this is, for example when you delete an entity from a long list of entities, browser shouldn't jump to the top.
Maybe simple solution would be to jump to the top only when hash has been specified in an url
On a traditional pageload, the page will be scrolled to the top. This is especially important when navigating from a long page to another page - being in the middle of the new page is disorienting. A short-term solution would be to use the following after a DOM write:
document.body.scrollTop = document.documentElement.scrollTop = 0;
The text was updated successfully, but these errors were encountered: