3 ms·
We have UseCounters showing that 0.04% of page views navigate back via the backspace button and 0.005% of page views are after a form interaction. The latter ar
by YeGoblynQueenne 11y ago
We have UseCounters showing that 0.04% of page views navigate back via the
backspace button and 0.005% of page views are after a form interaction. The
latter are often cases where the user loses data. Years of user complaints have
been enough that we think it's the right choice to change this given the degree
of pain users feel by losing their data and because every platform has another
keyboard combination that navigates back.
We're doing this via a flag so that we can control this behavior should there be
sufficient outcry.
oOh dear lord, that's a horrible idea. You make a change to your software to fix a
problem that is not caused _by_ your software? If a form is confusing enough
that the user thinks they have focus when they don't and ends up losing data
then that's an issue with the form, isn't it? Not the browser and not the
button.
- tremon 11y agoWhat makes you say that the problem is not caused by Chrome? I mean, Chrome is the user agent here, it handles both the form display and form input. However, I agree it's a poor solution. They could have chosen to track modification of form fields on the page and display a confirmation dialog when backspace is pressed.