News for hackers. Stuff that matters.
Re:Google Chrome to stop back-button hijacking by SquareWheel on Tuesday December 18, 2018 @11:35PM (#18713031)
>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.

Re:Google Chrome to stop back-button hijacking by ycombobreaker on Wednesday December 19, 2018 @09:40AM (#18715854)
Seems 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.

Re:Google Chrome to stop back-button hijacking by SECProto on Tuesday December 18, 2018 @11:53PM (#18713114)
> 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.

Re:Google Chrome to stop back-button hijacking by SquareWheel on Wednesday December 19, 2018 @12:17AM (#18713224)
>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-backs...