Re:Chrome removes Backspace to go back
by dredmorbius on Thursday May 19, 2016 @03:25PM
(#11733004)
I'd argue for both.
Caching local content as drafts-in-process does in fact make a great deal of sense.
How to present that poses a new set of UI/UX considerations. Perhaps not grave, but significant.
I do hold strongly that the "backspace to navigate* motif is either profoundly broken or tied to unacceptably weak state stickiness of editing content itself. It's a callousness, capriciousness, and lack of consideration on the part of browser developers to users concerns (as opposed to advertisers) which I'm very hard pressed to defend on any basis.
Caching local content as drafts-in-process does in fact make a great deal of sense.
How to present that poses a new set of UI/UX considerations. Perhaps not grave, but significant.
I do hold strongly that the "backspace to navigate* motif is either profoundly broken or tied to unacceptably weak state stickiness of editing content itself. It's a callousness, capriciousness, and lack of consideration on the part of browser developers to users concerns (as opposed to advertisers) which I'm very hard pressed to defend on any basis.