I expected the page to remember my position and keep me there so I don't have to scroll down through all of the themes again.
I'm automatically dropped back at the top. If I've scrolled through 50+ themes, I have to do that all over again.
Tested on Chrome (latest version) in OS X El Capitan
Cloudup: https://cloudup.com/c56piRW4Ka4
I think this is a nice-to-have UX and comes up in a lot of interactions with JS-driven web apps. One solution is to save the "x,y" position and return there. I know this is something we've had trouble with on front-end views with Infinite Scroll — paging, clicking into a post — then back, and poof! You've lost your place in the scrolling history.
On the other hand, clicking "All Themes" seems like an indication that you're going back to the main list so it might be logical to start at the top. What about supporting position only for when viewers use the browser back button?
CC @folletto for opinions and thoughts (in case Hyperion has discussed this).
It's a great suggestion.
We already tried at least a couple of times to do that, but it's not trivial (yes, I recall one of the problems was infinite scroll). It's definitely something that should happen on any "back" action, we just de-prioritized it due to more pressing issues.
Closing as low priority — let's revisit in the future.
Reopening. The reason is that while it's lower in priority after other issues regarding the showcase (i.e. completing the migration to one single showcase), it's still a major UX issue that keeps being reported to us even if it's a kind of frustration that not always surfaces.
This issue has been marked as stale because it hasn't been updated in a while. It will be closed in a week.
If you would like it to remain open, can you please you comment below and see what you can do to get things moving with this issue?
Thanks! 🙏
Reopening. The reason is that while it's lower in priority after other issues regarding the showcase (i.e. completing the migration to one single showcase), it's still a major UX issue that keeps being reported to us even if it's a kind of frustration that not always surfaces.
Still applies.
There's currently no team working on this, but it's still a major UX concern.
It also doesn't keep the state of filters. Every time I clicked on a theme and then went back, I had to set back up my theme filters again. Not sure if this requires its own issue.