too little, too late. The API for interacting with the back button in Javascript should never have existed in any capacity.
A new spam policy for “back button hijacking”
291–300 of 532 posts
Re: A new spam policy for “back button hijacking”
#292Ok, you can start with LinkedIn, I'll wait... If you are wondering how it works. You get a link from LinkedIn, it's from an email or just a post someone shared. You click on it, the URL loads, and you read the post. When you click the back button, you aren't taken back to wherever you came from. Instead, your LinkedIn feed loads. How did it happen? When you landed on the first link, the URL is replaced with the homep…
> You get a link from LinkedIn [or such]. You click on it, the URL loads, and you read the post. When you click the back button, you aren't taken back to wherever you came from. Instead, […] I've taken to opening anything in a new tab. Closing the tab is my new back button. In an idea world I shouldn't have to, of course, but we live in a world full of disks implementing dark patterns so not an ideal one. Opening in…
given the level of hostility most businesses have towards their customers, we should probably be opening links in disposable virtual machines
Re: A new spam policy for “back button hijacking”
#293Wait, how does one website (google.com) know what happens inside my browsing session on another website (bad-blog.com) after I click over? Hmmmmm
This sort of announcement just emphasizes the extent to which Google observes ALL your web browsing behavior, thanks primarily to their eyes inside Chrome browser.
You know those warnings when you install a browser extension, about all the things that extension will be able to see and do? Well so can Chrome itself…
Re: A new spam policy for “back button hijacking”
#294Earlier quoted context omitted.
> The problem is, there are two conceptions of the back button, and the browser only implements one. In web browsers, there is only one concept. There is no concept of "up one level in the heirarchy". If you want that make your own button in your website.
> There is no concept of "up one level in the heirarchy". If you want that make your own button in your website. https://lifehacker.com/how-to-move-up-one-url-level-in-chrom... *shrug *
> Chrome/Firefox: Ever been reading a site and wish not to go back to the last page you visited, but the last page in that web site's hierarchy?
This statement makes no sense to non-tech people. Most people don't think of sites hierarchically, at least not from a url path perspective.
Re: A new spam policy for “back button hijacking”
#295Earlier quoted context omitted.
On the other hand, "are you sure you want to exit without saving" is a good use-case. But I'd prefer that to be a setting I can allow for specific site.
Better yet, just save. Storage is cheap and fast these days. The “do you want to save?” idiom is a leftover from the days when a moderately sized document would take a noticeable amount of time to save and eat up a decent chunk of your floppy disk.
But what if you are leaving the page because you changed your mind, and don't wish to save the changes after all? This, for me, is the common case, so i would not want the browser to suddenly commit an unfinished draft.
Re: A new spam policy for “back button hijacking”
#296Reddit! I'm looking at you?
Those are all weird WebKit issues, and reddit not testing MobileSafari. It works perfectly on Chrome, if it was intentional they would have broken it on Chrome too. As always you can count on Apple/Safari team to not give a shit, not try to fix it, not reach out to reddit to ask them to fix it, etc.
You think Reddit does not test in their #1 browser?
Re: A new spam policy for “back button hijacking”
#297Re: A new spam policy for “back button hijacking”
#298Wait, how does one website (google.com) know what happens inside my browsing session on another website (bad-blog.com) after I click over? Hmmmmm This sort of announcement just emphasizes the extent to which Google observes ALL your web browsing behavior, thanks primarily to their eyes inside Chrome browser. You know those warnings when you install a browser extension, about all the things that extension will be able…
They've been crawling the web since inception
Re: A new spam policy for “back button hijacking”
#299Earlier quoted context omitted.
I don't use old Reddit, and haven't noticed this behaviour either.
Sounds like maybe some prevention against this is already implemented in either particular Android browsers, or ad blockers, maybe even for specific sites? Just speculating, I can't imagine a reason why they'd implement this especially for Safari. Other than A/B-testing or trash code that coincidentally doesn't work in all mobile browsers. Maybe they use the same AI that generates their fictious relationship stories…
My understanding is that Apple keeps Safari fairly broken and doesn't care to implement the Googleverse and leaves a lot of things E_WONTFIX. I have read speculation that broken Safari encourages apps in the App Store.
Re: A new spam policy for “back button hijacking”
#300Earlier quoted context omitted.
These are impossible to press with just one hand (or the bottom of my coffee cup in a pinch), though.
I use option + up arrow or option + down arrow sometimes, works the same as spacebar to page up / page down.
In which browser? Doesn't work in Firefox, unfortunately.