4 ms·
>warn before navigating This requires too much page context. A search field being partially filled is very different than a long registration form being worke
by SquareWheel 8y ago
>warn before navigating
This requires too much page context. A search field being partially filled is very different than a long registration form being worked on.
>give options for the keyboard shortcut
You said yourself, they released an extension for this.
- SECProto 8y ago> You said yourself, they released an extension for this. Oh was there an official one? At the time, the only extension I could find was some slightly-sketchy third party one that allowed you to set hot keys for many things. > This requires too much page context. A search field being partially filled is very different than a long registration form being worked on. Fair enough.
- SquareWheel 8y ago>Oh was there an official one? Yes, Google released an official extension to coincide with the update that removed the hotkey. https://chrome.google.com/webstore/detail/go-back-with-backspace/eekailopagacbcdloonjhbiecobagjci?hl=en https://chrome.google.com/webstore/detail/go-back-with-backs...
- ycombobreaker 8y agoSeems like there should still be enough context. A user risks lost workflow if they've done nontrivial form entry. Exactly where you set that bar may be debatable or measurable, but certainly there is a difference between a partial search query and a full address form, for example. Alternatively, the browser could just play it safe. I recall at one point the old Opera would prompt if unsaved form edits were present, on any navigation attempts (clicking away or browser back button/backspace). This saved me on many occasions and I never remember being annoyed by over-notification.