Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A new spam policy for “back button hijacking”

developers.google.com

Post reply on HN
Print view View original

361–370 of 532 posts

Re: A new spam policy for “back button hijacking”

#361

Post by embedding-shape »

CDRdude wrote: post #356
embedding-shape wrote: post #343

Earlier quoted context omitted.

Even manually typing reddit.com/r/all (or r/All, which was a workaround for a while) in the address bar on iOS Safari redirects you to reddit.com/. Since I'm guessing you're not browsing reddit.com, what client are you using?

This is available for me on iOS https://old.reddit.com/r/all/

I'm not sure what exact device you're using, but on iPhone 12 Mini, old.reddit.com is borderline unusable, very different experience compared to if you could access r/all like before via the actually usable web+mobile version, a comparison: https://imgur.com/a/AVGjjCN

Anyways, the end result has been I don't use reddit at all on the phone, so kind of ended up being good for me anyways.

Re: A new spam policy for “back button hijacking”

#363

Post by MrMember »

Havoc wrote: post #220

Great. Can we do ctrl-f search hijacking next. So jarring when websites replace core functionality with their own broken crap because they think they’re special. Some also seem to hijack right click menu now

Github hijacks '/' and it's really annoying, it gets me all the time.

Re: A new spam policy for “back button hijacking”

#364

Post by chongli »

miki123211 wrote: post #136
chongli wrote: post #7

Earlier quoted context omitted.

It really comes down to JavaScript. The web was fine when sites were static HTML, images, and forms with server-side rendering (allowing for forums and blogs).

The web was not fine. If you wanted to accomplish anything more substantial than reading static content (like an email client that beeps when you get an important email, or a chat app that shows you new messages as they come in), you needed to install a desktop app. That required you to be on the same OS that the app developer supported (goodbye Linux on the desktop), as well as to trust the dev a lot more. We seem t…

I use a desktop mail client. I have always used desktop applications. I have never had any desire to use web mail clients. Likewise for office suite applications. A true desktop spreadsheet, word processor, and slide deck are always superior.

The web as an application platform has always been a half-baked, second class, inferior experience for the user. It has always been about developer convenience at the expense of the user. No thank you!

Re: A new spam policy for “back button hijacking”

#366

Post by Arainach »

blooalien wrote: post #206
Arainach wrote: post #135

Earlier 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 *

Those are third party extensions, not browser features, and they're not consistently applied.

Going from an image to a root domain is not a hierarchy and as a pathological data hoarder who has downloaded a lot of images from a lot of sites I don't understand why I'd ever want that feature. It's wild that that's their first example use case on the article.

Similarly, going from page N of results to page 1 isn't "up a level in heirarchy".

Re: A new spam policy for “back button hijacking”

#367

Post by arcfour »

optionalsquid wrote: post #232
arcfour wrote: post #160

Earlier quoted context omitted.

Opt in features are a great way to increase user frustration and confusion. See the whole new geolocation API they had to make for browsers since people would perma-deny it reflexively and then complain that geolocation features weren't working.

That's a good point, though I'm not familiar with the (changes to the) geolocation API you mention. Do you have any recommendations for reading up on that development?

Sure, I should have said geolocation element, since the original API still exists and is used: https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/...

Re: A new spam policy for “back button hijacking”

#368

Post by arcfour »

hnlmorg wrote: post #208
arcfour wrote: post #158

Earlier quoted context omitted.

As a user, I really don't care about the supposed purity or correctness of a website's tech stack. When I click "back" I want to go back to what I think the previous page was.

As a user, I don’t really care about the building materials used in construction. But that doesn’t mean builders should cut corners.

A building collapse and a poorly built website UI are completely different in terms of actual risk.

Re: A new spam policy for “back button hijacking”

#369

Post by hmokiguess »

It's getting very tiring seeing things that could be first-class user defined controls baked in the browser so that you have true agency over the behaviour being done like this

It's like the other thread from before where LinkedIn scans for your extensions, the fact they can do that without prompting for permission from the user is baffling

Re: A new spam policy for “back button hijacking”

#370

Post by matthewkayin »

eviks wrote: post #215
miki123211 wrote: post #132

Earlier quoted context omitted.

The problem is, there are two conceptions of the back button, and the browser only implements one. One conception is "take me back to the previous screen I was on", one is "take me one level up the hierarchy." They're often but not always the same. Mac Finder is a perfect example of a program correctly implementing the two. If you're deep in some folder and then press cmd+win+l to go to ~/Downloads, cmd+up will get y…

You're describing 2 different concepts, back and up, not 2 backs

Exactly. It is crazy that they described MacOS finder as doing this correctly when finder has no concept of up, it only has a back.
Post reply on HN