I was curious how that works, so I clicked into the ouibounce repo and read the README. I still don't get how it works, but I enjoyed how they flirt with self awareness:
> it's very easy to create something spammy-looking.
...and then they list "good" uses that are... all spammy.
These actions can be used to infer possible intent to leave: scroll up (to reveal address bar on mobile), move mouse toward top of viewport (to move mouse toward address bar), swipe down (to reveal address bar on mobile), loss of UI focus, probably others.
I hate these patterns, and they are 100% appropriately described as dark. I and the other devs spent months at one place arguing with a PM about how janky and broken the third-party intent-to-leave detector they injected using Google Tag Manager without dev involvement made our app feel. (GTM was the product that convinced me Google gave up on not being evil)
Okay, so it's all indirect? I usually just ctrl-w, and beyond the browser native dialog that sites can use to ask if you want to confirm saving your work or something, I wasn't aware of any way to intercept that or do anything about it.
> it's very easy to create something spammy-looking.
...and then they list "good" uses that are... all spammy.