4 ms·

Yep, it's completely jacked. Very annoying. Of course, back in Twitter also randomly loses your place, too. I guess it's one of those "we're a big deal site now

by dilap 4y ago

Yep, it's completely jacked. Very annoying. Of course, back in Twitter also randomly loses your place, too. I guess it's one of those "we're a big deal site now" checklist items: Fuck up the back button.

dieselgate 4y ago
In regards to what you’ve mentioned about hitting back on Twitter and losing your scroll position - I think this is a difficult technical problem so solve in an elegant and reproducible way. We’ve attempted to address this back location issue at my work for an “infinite scroll” feature and can only get it right about half the time and believe that’s handled mostly by the browser. We’ve specifically looked at how YouTube handles this - and it’s about the same success rate for them. Oh well even HN will always mess up your scroll position when hitting back so it goes
- dilap 4y ago
  As a non-web dev, it is mystifying to me that this is hard. But, taking it as true (for some arcane reason), then perhaps they should change the design of their site so that popping away from the timeline isn't a part of the normal usage flow! Specifically, if you want to expand the conversation under a tweet, you tap it, which takes you to a new page; when you're done, you want to continue reading your timeline. If making the back button can't be made reliable, then it seems a design that simply expands the thread off to the right or inline below or in a popup, without leaving the timeline page, would work much better.
- thirdsun 4y ago
  > for an “infinite scroll” feature I think I found the problem.
  - dieselgate 4y ago
    Haha yeah not my design and personal choice. But it’s really supposed to be “infinite scroll for the first 3 pages of results than see more button”. I understand the business decisions into implementing “infinite” scroll, though, and at the very least it’s an interesting problem to take on. Compared to “make this button bigger”

by dilap 4y ago

dieselgate 4y ago

In regards to what you’ve mentioned about hitting back on Twitter and losing your scroll position - I think this is a difficult technical problem so solve in an elegant and reproducible way. We’ve attempted to address this back location issue at my work for an “infinite scroll” feature and can only get it right about half the time and believe that’s handled mostly by the browser. We’ve specifically looked at how YouTube handles this - and it’s about the same success rate for them. Oh well even HN will always mess up your scroll position when hitting back so it goes

dilap 4y ago
As a non-web dev, it is mystifying to me that this is hard. But, taking it as true (for some arcane reason), then perhaps they should change the design of their site so that popping away from the timeline isn't a part of the normal usage flow! Specifically, if you want to expand the conversation under a tweet, you tap it, which takes you to a new page; when you're done, you want to continue reading your timeline. If making the back button can't be made reliable, then it seems a design that simply expands the thread off to the right or inline below or in a popup, without leaving the timeline page, would work much better.
thirdsun 4y ago
> for an “infinite scroll” feature I think I found the problem.
- dieselgate 4y ago
  Haha yeah not my design and personal choice. But it’s really supposed to be “infinite scroll for the first 3 pages of results than see more button”. I understand the business decisions into implementing “infinite” scroll, though, and at the very least it’s an interesting problem to take on. Compared to “make this button bigger”