archives html user interface menu selection retention after refresh
I have just started studying the archives feature and I've noticed that if I select "Most Active" in the top menu and then I refresh my browser, the refreshed screen jumps back to Recent after the refresh. In fact, if ANY of the five menu items across the top are selected and then a browser refresh is performed, the result is that one is always taken back to the Recent menu item. It was not apparent to me for a couple of days that this was happening and I'd convinced myself there was some bug in the Recent vs. Most Active lists because the Most Active list changed entirely after I did a refresh, when, in fact, I was then viewing the Recent list again. Confusing.
Is there some way that whatever menu item was being viewed before a refresh could be retained so that the same menu item is shown after a refresh?
Thinking this through even further, I suppose a side-affect of this request could be that visiting the same page much later (ie. not immediately after a refresh) may result in the page NOT defaulting to the Recent menu item any longer (unless once could clear the "last menu item" memory when the viewer moves AWAY from or closes the page). I don't have enough familiarly with the interface to suggest if this would be a bad side-effect, or good, but would this, indeed become a side-affect that would have to be thought through?
On 6/28/23 10:38 PM, Ken Alker wrote:
I have just started studying the archives feature and I've noticed that if I select "Most Active" in the top menu and then I refresh my browser, the refreshed screen jumps back to Recent after the refresh. In fact, if ANY of the five menu items across the top are selected and then a browser refresh is performed, the result is that one is always taken back to the Recent menu item. It was not apparent to me for a couple of days that this was happening and I'd convinced myself there was some bug in the Recent vs. Most Active lists because the Most Active list changed entirely after I did a refresh, when, in fact, I was then viewing the Recent list again. Confusing.
This is the expected behavior. the various Recent, Most Active, ... tabs
use # fragments to switch the view, but these don't change the URL that
the browser went to (the one in the browser's address bar) so a refresh
goes to that original URL which defaults to the Recent view.
Is there some way that whatever menu item was being viewed before a refresh could be retained so that the same menu item is shown after a refresh?
Probably not without significant redesign of the web UI.
Thinking this through even further, I suppose a side-affect of this request could be that visiting the same page much later (ie. not immediately after a refresh) may result in the page NOT defaulting to the Recent menu item any longer (unless once could clear the "last menu item" memory when the viewer moves AWAY from or closes the page). I don't have enough familiarly with the interface to suggest if this would be a bad side-effect, or good, but would this, indeed become a side-affect that would have to be thought through?
It would depend on how the feature was designed, but this is probably moot as such a feature is unlikely to be implemented as it seems the potential benefit doesn't warrant the additional complexity.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Ken Alker -
Mark Sapiro