[teqsun]

That's fantastic stuff!

Minor UX notes: - clicking the header doesn't navigate back to the "home" screen - singular page history (so the back button doesn't take you back to the previous page state)

Combined it made it not intuitive for me how to "get rid" of the selection I'd created (I eventually figured it out, but the previous two points were what I intuitively tried first)

[klimeryk]

> clicking the header doesn't navigate back to the "home" screen - singular page history (so the back button doesn't take you back to the previous page state)

Could you describe in more detail this? I'm not sure I agree that state changes should be pushed to browser history. In my experience this usually leads to confusing user experience. But that might be also just years of conditioning and I'm missing some best practices. So happy to learn more.

[teqsun]

My natural instinct to return to the "default" view (as in, how the page looked the very first time before I interacted with anything) was to click the header text at the top (that says "deal with it"). Same as you click the "Hacker News" text at the top to return to the default home page view.

Just as something to be a quick "oops, didn't want to use that image, I want to go back to how the site is when I first visited it", and essentially wipe the state.

The history stuff is secondary, since that was my second instinct after trying to find and hit a "home" button, just from my personal UX perspective.