Note that the HTTP 1.1 spec disagrees w/ @sebmarkbage "history mechanisms SHOULD NOT try to show a semantically transparent view of the current state of a resource. Rather, a history mechanism is meant to show exactly what the user saw at the time when the resource was retrieved"https://twitter.com/sebmarkbage/status/963081665764458496 …
-
Show this thread
-
Replying to @mixonic
Is your point that the HTTP 1.1 semantics is good UX, bad UX or just right due to being a spec?
3 replies 0 retweets 1 like -
Replying to @sebmarkbage
I'm not sure about the UX. For example if you click logout on a page then click "back" HTTP suggests you would see the exact screen from when you were logged in. "Semantic transparency" suggests you would see... what? Updated content? An error that you are logged out?
1 reply 0 retweets 1 like -
Replying to @mixonic @sebmarkbage
But regardless I think you should tread carefully, the browser might be working against your intention.
1 reply 0 retweets 1 like
Replying to @mixonic @sebmarkbage
I think that without a loading spinner, changing what the user last saw is unexpected.
6:18 PM - 12 Feb 2018
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.