[conartist6]

Feedback: navigation within a slide deck needs to happen with `history.replaceState` not `history.pushState` so that it is possible to leave the page again after scrolling around a bit. As it is the back button forces me to back out through my entire scroll history to get to the web page I was previously on which is an anger-inducing experience I would not want to subject others to.

As mentioned if plain text is your goal it would be really nice if there were some way to serve the content as plain HTML as a backup

[gregorywegory]

That was something I thought deeply about. I decided that an imaginary user would see a page change as a navigation event. Pressing back and having the whole thing poof could be just as anger inducing. Most SPAs use some type of router to do just that.. I imagine I won’t hear from anyone who prefers it that way so until I can afford some user testing I won’t know. Quite a bit of anxiety about that one. I had initially used replaceState…

Yes, plain text to create it not displayed as plain text. I didn’t write the post so the title may be a little misleading. Flashy JS heavy output for minimal input is the point.

[grog454]

I scrolled down. Then I scrolled up. Then I scrolled down. Then I scrolled up. Then I was ready to leave so I hit the back button. Only instead of that happening, I was scrolled up, and down, and up, and down, and up, and then I could leave.

Taken to the extreme, I think it becomes more apparent which choice is better.

[gregorywegory]

Yes you’re right. I’ll switch that off.

[nixpulvis]

We need to remove the entire History API from the web.

Bring back the back button!

[mrgoldenbrown]

Yeah, same problem here. this was annoying enough for me to close the browser and give up.

[gregorywegory]

Sorry to hear that. Maybe I should add a user setting?