91–100 of 156 posts
I've implemented quick exit/escape buttons for a few organisations over the years and have spent a bit of time thinking about the limitations. This pattern is definitely better than most and it is refreshing seeing they put some resources into it. In my professional experience, organisations often chose the "a link to another site like google is fine" option to save money and time while still getting to boast about t…
Earlier quoted context omitted.
That and they dont want butt dialing 911 to be easy
Quickly press the power button 5 times if you have an android phone and see what happens. This has got to be the absolutely worst idea ever and it's enabled by default!
The gov.uk Design System calls this the "Exit a page quickly" pattern [1], with an associated component [2]. It can be activated by clicking the Shift key three times. There's this nice blog [3] that explains why they chose Shift instead of other keys, and also gives a nice overview of the pattern. [1] https://design-system.service.gov.uk/patterns/exit-a-page-qu... [2] https://design-system.service.gov.uk/components/…
This is nice but how, as a user, do you learn it exists?
> Interruption page
> Create a page to explain Exit this page to users.
> You must show this page after the start point of your service, but before the page where the user will see the Exit this page button for the first time.
> On longer services, you might need more than one interruption page.
Why don't they inform users about how to properly use private mode, which works with any website, instead of rolling their own solution, which the user has to learn just for that one website?
Isn't this exactly why browsers implemented "private mode"? Why don't they inform users about how to properly use private mode, which works with any website, instead of rolling their own solution, which the user has to learn just for that one website?
Isn't this exactly why browsers implemented "private mode"? Why don't they inform users about how to properly use private mode, which works with any website, instead of rolling their own solution, which the user has to learn just for that one website?
On top of that, informing users requires them to open up the website in the first place… leaving it in… the history.
Earlier quoted context omitted.
This would also leave intact cookies, local/session storage, indexeddb, caches. All of which abusers do actually check, when controlling their victims.
I'm sure 99% don't? Unless your abuser is a CS major
I am 100% sure that some do, thanks to firsthand life. And any doing it, is enough to get people dead, even if 99% don't. And yes, CS majors can be abusers, too.
[0] https://www.esafety.gov.au/key-topics/domestic-family-violen...
Isn't this exactly why browsers implemented "private mode"? Why don't they inform users about how to properly use private mode, which works with any website, instead of rolling their own solution, which the user has to learn just for that one website?