201–210 of 594 posts
Earlier quoted context omitted.
Safari added protection for 'unsaved forms' when closing a window/tab in v3, which was released about 9 years ago.
Great. I'll get right on installing Safari on my Ubuntu machine.
Chrome / Chromium have a habit of making these arbitrary changes that seriously annoy some (arguably small) percentage of their users, while claiming that it makes it simpler / better for everyone else, while explaining impatiently why it's infeasible to make the now missing feature a configuration option. Evidently the kinds of people that can't be bothered going into the Advanced Configuration Settings page would b…
Chrome / Chromium have a habit of making these arbitrary changes that seriously annoy some (arguably small) percentage of their users, while claiming that it makes it simpler / better for everyone else, while explaining impatiently why it's infeasible to make the now missing feature a configuration option. Evidently the kinds of people that can't be bothered going into the Advanced Configuration Settings page would b…
Speaking of annoying things Google has done lately, they recently updated Android's Google Keyboard completely changing the layout, keysize and removing most of the secondary (press and hold for more characters) keys. It has become almost impossible to type with it but I haven't found another keyboard with a good theme, haptic feedback and good suggestions. I miss the days Google used to cater to power users.
Earlier quoted context omitted.
This is great news. For some use cases, backspace-as-back is a disaster waiting to happen, for example, in a complex web app used in some time-critical task and that requires occasional deleting of text but can lose state or take a while to reload if you accidentally hit back. If you hit backspace without having a text field focused, the whole thing dies and needs to be reloaded and possibly checked to make sure it's…
Giant web forms have been a usability disaster since day one. Accidental back button, link click, window close, session timeout, etc, increase the chance of a failure and need to re-enter the entire form. Whereas for at least 40 years desktop software has given you a "sure you don't want to save?" option.
Typical myopic power users...
Chrome / Chromium have a habit of making these arbitrary changes that seriously annoy some (arguably small) percentage of their users, while claiming that it makes it simpler / better for everyone else, while explaining impatiently why it's infeasible to make the now missing feature a configuration option. Evidently the kinds of people that can't be bothered going into the Advanced Configuration Settings page would b…
Speaking of annoying things Google has done lately, they recently updated Android's Google Keyboard completely changing the layout, keysize and removing most of the secondary (press and hold for more characters) keys. It has become almost impossible to type with it but I haven't found another keyboard with a good theme, haptic feedback and good suggestions. I miss the days Google used to cater to power users.
Earlier quoted context omitted.
Does Chrome not prompt you about losing un-submitted changes to a form when triggering a navigation event?
(1) No, it does not. (2) The concept of a "form" is less and less clear in the realm of web apps.
In the context of html in a browser, a form isn't a concept to be debated, it's a well understood element defined in the html standard.
If an app chooses to not use html forms and instead uses something like contenteditable to create its own editing environment, then you likely have much bigger issues than the back button.
When using a laptop with a sensitive touchpad, this can get really bad.