Isn't this going to break a lot of React Router navigation? Are they going to manually check every website to see if their manipulation of the history is legit or spammy?
A new spam policy for “back button hijacking”
491–500 of 532 posts
Re: A new spam policy for “back button hijacking”
#492Earlier quoted context omitted.
Single Page Applications use the History API to create a working back/forward history within the SPA. This will cause you to navigate away on use, and potentially lose data.
That sounds like a design failure.
It's not, I don't know why you'd think that.
Re: A new spam policy for “back button hijacking”
#493Re: A new spam policy for “back button hijacking”
#494Broken back buttons have been one of my biggest complaints since we enabled SPAs to access the history API in the first place. I don't see it as a net win so far, but maybe a decade later we can solve it?
Re: A new spam policy for “back button hijacking”
#495I wish the browsers had a function of disabling all keyboard shortcuts of a website. I binded Ctrl+E to opening a new tab just beside the current tab (built-in hotkey in Brave). It's frustrating to see it changed to something like opening the emoji menu on Discord.
Ctrl+f is a bad offender. No I don't want to use your contextual search. I want to search for this word on this page!
Ctrl-f for page search and ctrl-k for website search[1].
[1] https://fmhy.net
Re: A new spam policy for “back button hijacking”
#496I wish the browsers had a function of disabling all keyboard shortcuts of a website. I binded Ctrl+E to opening a new tab just beside the current tab (built-in hotkey in Brave). It's frustrating to see it changed to something like opening the emoji menu on Discord.
Rather than outright disabling it, I wish it was a permission the site would have to request. That way trusted sites that used it responsibly could be given permission, but it could not be used by any random site.
This is the way.
Re: A new spam policy for “back button hijacking”
#497[deleted]
Re: A new spam policy for “back button hijacking”
#498Earlier quoted context omitted.
Ctrl+f is a bad offender. No I don't want to use your contextual search. I want to search for this word on this page!
Ctrl-f for page search and ctrl-k for website search[1]. [1] https://fmhy.net
Agreed. I also like slash / to focus the primary input like on youtube
Re: A new spam policy for “back button hijacking”
#499Some Microsoft sites have been very guilty of this. They are the ones that stick in my head in recent memory.
Microsoft Learn. I first noticed this a couple years ago not long after they changed the url from docs.microsoft.com to learn.microsoft.com. Each time you went from a google search to a learn page it would load, redirect to login.microsoftonline then go back to the learn page. Hitting back in the browser took you back to login.microsoftonline which forwarded you back to the learn page. Hitting back twice in quick succession took you back to the docs page then forwarded you to login.microsoftonline. Easier to close the tab and start again. Maybe it was something to do with the changes to the site to make it more like an online college, as that portion requires signin, but I’m just after first party doco! Dunno if this still happens today but at the time I was browsing docs every other day and it was super frustrating. Note: it only did this if you were already signed in elsewhere, something triggered Microsoft sso check. Similar to if you go to portal.office.com, it is a page that requires sign in and so does the login.microsoftonline redirect to check for active tokens.
Re: A new spam policy for “back button hijacking”
#500Earlier quoted context omitted.
Regarding Google and LinkedIn, I keep complaining to them about a stupid feature of Gmail. If I get an invitation from someone, Gmail puts "accept" as a button in the subject of the email - so if you aren't careful you can accept while you are scrolling through the subject lines. That is just the worst feature to put in their subject line.
Does "accept" support "undo send"?
I don't think so. At least not from the inbox, where it happens. I'm not in the message - I'm just dragging on the subject lines to scroll, and these "hotspots" light up on the right portion of the subject.