5 ms·

So, you clicked 'back', and it took you back to the last page you viewed. And that's unexpected behaviour? I would theorise that the only reason you expected t

So, you clicked 'back', and it took you back to the last page you viewed. And that's unexpected behaviour? I would theorise that the only reason you expected the back button to return you to HN was that your expectations have been poisoned by having to deal with the broken behaviour of sites like this made in Flash rather than HTML5.

ams6110 16y ago
Like it or not, that's the reality. Most people's expectations of what "back" does are influenced by their years of experience with Flash and other plugin-based content.
- bouncingsoul 16y ago
  Parent comment is currently at -2 points, but a comment 10 days ago expressing the exact same opinion has 29 points: http://news.ycombinator.com/item?id=1883654 http://news.ycombinator.com/item?id=1883654 Online discussion confuses me.
smackfu 16y ago
In an AJAX world, "last page you viewed" gets a bit fuzzy.
Waywocket 16y ago
>So, you clicked 'back', and it took you back to the last page you viewed. And that's unexpected behaviour? Well, the site is basically a few pages of content split into an endless number of excruciatingly tiny chunks. Each 'page' is really a paragraph (and doesn't actually entail a page load) - nrmally I'd expect 'back' to take me back an entire page, rather than a single paragraph. If you're going to use ajax to slice pages into tiny sections, it's far more usable if you then make the back button act as if you hadn't done such a stupid thing in the first place.