4 ms·
Damn, why are TechCrunch hijacking the browsers back button behaviour? I had to close down my browser instance complete and then open a new one to come back to
by GEBBL 6y ago
Damn, why are TechCrunch hijacking the browsers back button behaviour? I had to close down my browser instance complete and then open a new one to come back to this thread. Awful.
- bigp3t3 6y agoI believe it changes the URL when you move on to the next article
- GEBBL 6y agoHmm, it’s stopped happening for me now.
- deleted 6y ago[deleted]
- radoslawc 6y agoIf you scroll down below comments section URL changes to https://techcrunch.com/ https://techcrunch.com/ then if you press <- button in browser it changes to previous: https://techcrunch.com/2020/05/08/microsoft-surface-go-2-review/ https://techcrunch.com/2020/05/08/microsoft-surface-go-2-rev... If you do it 6 times you'll have to "go back" six times. Maybe not back button hijacking, but outcome's the same, and it's pretty annoying I admit.
- matijs 6y agoTechCrunch apparently force a 307 Temporary Redirect to some advertising.com domain first :/
- postexitus 6y agoanother reason to use Firefox
- nfoz 6y agoI blame browsers for implementing such an obnoxious anti-feature.
- emilfihlman 6y agoIt's not directly an issue with TechCrunch but the lack of an api that does not push a history state OR pollute your history. Ie you can't change the visible URL without at least one of these happening (and it's infuriating)!
- fiskfiskfisk 6y agoIsn't that what the `History.replaceState()` method achieves? https://developer.mozilla.org/en-US/docs/Web/API/History/replaceState https://developer.mozilla.org/en-US/docs/Web/API/History/rep...
- emilfihlman 6y agoNope, it will result in a history entry added to your history (even if nothing is added to the immediate backwards forwards history).
- Chris2048 6y agoTBH, Maybe HN should just avoid sites like TC, and stick to, say, https://www.tomsguide.com/reviews/microsoft-surface-go-2 https://www.tomsguide.com/reviews/microsoft-surface-go-2