For example the main Google Translate page.https://translate.google.comIf you try clicking the Back button in the web browser it doesn't actually go back to the previously loaded page.
Try loading google translate, check the url. Then translate a word and check the url again.You go to translate.google.com, but it redirects you to translate.google.com/?sl=auto&tl=en&op=translate. so now you're on a redirected page and when you click back you get back to translate.google.comWhen you start writing words it spams you with redirects so now your browser thinks you visited hundreds of pages
Nigger-end developers hijack it with with JS.If you ever have a chance, shoot a front-end developer, like, just kill them, please.
garbage website coding most of the time. its not intentional most of the time but sometimes it is. its called dark patterns.
>>106648947https://developer.mozilla.org/en-US/docs/Web/API/History_API
Usually it's because some idiot wrote the entire site as what they call a single-page application which is just a Javascript program where the links don't actually open different pages, but instead call Javascript functions which rewrite the current page. There is a Javascript API which is supposed to make the back button and other history stuff work on these sort of sites, see >>106650902, but the programmers fuck it up.
>>106648947Right clicking (or press-hold) the back button in most browsers will allow you to pick how many pages to go back
>>106648947Some websites are using app layer and things you click are happening inside of this faggotry.
