4 ms·

The page spams my browser's back button history when I scroll, and displays a white screen for the first 2 seconds if I turn off JS.

• rightbyte 5y ago
  Ye it seem to be a very bad design choice to hijack the back button each time you scroll by an anchor. A bad design choice would be to do that when clicking in the table of contents.
  • fathyb 5y ago
    You convinced me to fix the TOC on projects I work on! I'll use "history.replaceState()", so that the address bar gets updated but the back button doesn't get hijacked.
    • rightbyte 5y ago
      Glad to be of service! =)
• dang 5y ago
  "Please don't complain about tangential annoyances—things like article or website formats, name collisions, or back-button breakage. They're too common to be interesting." https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html The greater problem is that these comments tend to get upvoted and then stick at the top of the thread, choking out more interesting discussion—but it's harder to do anything about that.