The better UX could have been making this a regular option, and (by default) showing a warning dialogue if using backspace to navigate would clear out a form.
Haven’t done much web UI, but I’m guessing that are too many way to skin the “form” cat to account for.
In any case, first time I’ve read any reasoning on removing it. Chrome killed it long ago and I was using an extension to re-enable it. Probably could have done as I just did in Firefox, fiddle with the config.
Form and input elements are a very standard thing, and while you can certainly do crazy stuff with it, even a simple check if you typed into an input/textarea, or changed a select without submitting the form element, should be sufficient.
I guess the problem might be detecting the submission (because oftentimes there’s custom logic for that) but maybe better just display the warning than lose data. Worst case you’ll just ignore it, best case the devs fix it so that it doesn’t show up when it shouldn’t.
The better UX could have been making this a regular option, and (by default) showing a warning dialogue if using backspace to navigate would clear out a form.
Haven’t done much web UI, but I’m guessing that are too many way to skin the “form” cat to account for.
In any case, first time I’ve read any reasoning on removing it. Chrome killed it long ago and I was using an extension to re-enable it. Probably could have done as I just did in Firefox, fiddle with the config.
Form and input elements are a very standard thing, and while you can certainly do crazy stuff with it, even a simple check if you typed into an input/textarea, or changed a select without submitting the form element, should be sufficient.
I guess the problem might be detecting the submission (because oftentimes there’s custom logic for that) but maybe better just display the warning than lose data. Worst case you’ll just ignore it, best case the devs fix it so that it doesn’t show up when it shouldn’t.