Any progress here? You realize with the bug in place, your "next" and 'previous" nav buttons fail often because the system looses it's place and you have to navigate back to the main order screen.
Is this even being worked on?
There's progress but not in the way that I had originally expected.
For context, the admin currently stores much of its state client-side. When the page refreshes, some of this state is lost. Hence what you're seeing with the loss of selected filter and the loss of prev/next.
We had attempted to solve this by persisting some state across page refreshes but this was creating side effects that were breaking other parts of the admin, hence the rollback a couple months ago.
Since that time, we've decided to move to storing this state server-side but this is a larger effort.
The unfortunate part of this is that it will be longer yet before this issue is solved.
Yes, it's still being worked on. As mentioned, it's part of a larger effort which has been underway for some time now. We're nearing the end of that effort and have started rolling out these changes to store owners this week and will continue for the next few weeks. These changes are resulting in performance improvements in a number of places and is allowing us to address this usability concern, as well.
Sort of. We had a bunch of discussion internally to decide on what to do.
The question we asked was "what do people expect to see when they click to see the list of Orders?" Should it return to the last viewed page (including pagination)? What happens when new orders come in? Do people know they're not looking at all orders but maybe only a subset of orders?
For now, different behaviours occur depending on where you click:
This is similar to how Gmail does it when you've done a search, where they present a big back button. We'd love your feedback on this and whether this meets your expectations.
|an hour ago|
|2 hours ago|