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

501–510 of 532 posts

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

#501

Post by inetknght »

creatonez wrote: post #340
phkahler wrote: post #325

Earlier quoted context omitted.

>> There's a place for it within SPAs - you want the browser back button to retrace your path through screens in the application, not exit it, unless you are already on the first page. No, You SPA should have it's own back button within the app. My browser back button should get me out of there no matter what.

Then you lose the benefit of having the current URL actually linking to the resource you are currently viewing. If the app is not properly making use of URL modification and the history API, getting back to where you were requires navigating the whole maze each time.

You can regain that benefit by building an actual website instead of a shitty single-page "application"

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

#502

Post by chongli »

socalgal2 wrote: post #173
ryandrake wrote: post #25

Earlier quoted context omitted.

I’d go back in a heartbeat. Making the web a software SDK was the worst thing to happen to it.

So, apparently you don't use google maps (or any other mapping website)

Doesn't need to be a website, can be a native app. Native map apps on phones are superior to web app maps anyway.

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

#503

Post by al_borland »

boomlinde wrote: post #261
lamasery wrote: post #11

Earlier quoted context omitted.

IIRC the Azure “portal” does this. Also likes to not record things as navigation events that really feel like they should be. Hitting back on that thing is like hitting the back button on Android, it’s the “I feel lucky” button. Anything could happen.

Having used Azure I believe that this is the result of pure, distilled incompetence rather than malicious intent.

This maybe true, but I don’t think a company as large as Microsoft can get a pass. There is no excuse for them not being able to handle a back button properly. They are worth trillions of dollars, run some of the biggest sites on the internet, and defined much of how the web worked for an entire computing era.

They should have their feet held to the fire on this.

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

#504

Post by bryanhogan »

sam1r wrote: post #478
ffsm8 wrote: post #91

I would like to mention that Google own SPA framework, angular, has redirect routes which effectively do back button hijacking if used, because they add the url you're redirecting from to the history. https://angular.dev/guide/routing/redirecting-routes

That's only because SPAs routing maybe internal for that particular app. In that case, the UI/UX to end user is *only* possible and smooth when they hijack the back button as such.

Yeah, I think people are forgetting that if we want PWAs to behave and function like "native apps" that this functionality is needed.

I revently built an app with SvelteKit + Capacitor and had to implement the stack-based navigation one expects from a phone app myself.

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

#505

Post by nesk_ »

rat_on_the_run wrote: post #383

I 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.

Actually, you can do that with Firefox, either per site or as a global policy.

https://superuser.com/a/1317514

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

#506

Post by int0x29 »

HappMacDonald wrote: post #484
fluoridation wrote: post #445

Earlier quoted context omitted.

That's relatively easy to work around. Right-clicking on the back button lets you go back several steps at once. I don't know about Chrome, but it does work on Firefox.

AFAICT just holding left-click for half a second has the same effect. That's been my go to since the little triangle dropdown vanished from the back button (checks watch).. uh, some time in the nineties mebe?

Firefox had it in 2010. I don't remember when IE ditched it.

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

#508

Post by boomlinde »

al_borland wrote: post #503
boomlinde wrote: post #261

Earlier quoted context omitted.

Having used Azure I believe that this is the result of pure, distilled incompetence rather than malicious intent.

This maybe true, but I don’t think a company as large as Microsoft can get a pass. There is no excuse for them not being able to handle a back button properly. They are worth trillions of dollars, run some of the biggest sites on the internet, and defined much of how the web worked for an entire computing era. They should have their feet held to the fire on this.

Hear, hear.

I mention it not to excuse Microsoft's sins, but to the contrary to point out that malicious intent as a criteria isn't such a good idea after all, when there are such obvious cases of incompetence and malice being practically indistinguishable.

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

#509

Post by nailer »

ffsm8 wrote: post #91

I would like to mention that Google own SPA framework, angular, has redirect routes which effectively do back button hijacking if used, because they add the url you're redirecting from to the history. https://angular.dev/guide/routing/redirecting-routes

getAngular was an online JSON storage service. The guys reused their code when they went to work in DoubleClick at Google. Not made by Google not Google’s framework and plenty of Google people think it’s rubbish.

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

#510

Post by dspillett »

cortesoft wrote: post #373
dspillett wrote: post #191

Earlier quoted context omitted.

> 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…

I have always done this, although mostly so I don’t have to reload the page I am coming from when I hit the back button.

This too. Particularly required for broken SPA-style sites that reset when you re-enter instead of properly maintaining their state, or infinite scroll based pages that don't remember where you scrolled to/through.
Post reply on HN