It’s not browsers but poorly-designed JavaScript: if you use a standard HTML form all browsers will preserve state and resubmit it for you on retries. The problem is when you have JavaScript altering the form but not reimplementing the standard state management, and since few sites do more than casual testing these days it tends to require a number of user reports before that’s prioritized since it’s so easy for lazy developers to blame the error condition rather than accept that handling it is part of the job.
- External editor for textbox input
- Save form data to a local disk file
- Recall form data from a disk file (on the same or a different webpage than it was saved from)
- Replace scripts in the document
- Document/application mode switch
- Disable rich text editing
- Specify a remote filename when uploading files using forms
You might be interested in https://decentraleyes.org/
I consider this the biggest loss in that transition.
(Just though of another example: Picture in Picture video playback, like Firefox recently added and Chrome and Safari have technically already had for a while.)
They’re back now for mobile with react and ionic. In a weird what comes around way.
Ah, I still remember native buttons being introduced. Good times, back when browsers could introduce features that seem so obvious in retrospect - such as spell check in text boxes. Feels like all the low-hanging fruit has been picked by now. (Or is it? Firefox's integrating a password manager feels pretty similar.)
Great overview, though. I feel like my history with the web has been almost the same as the author's, and this brought back a lot of good and not-so-good memories.