It’s not for this, of course. It’s because in the world of single page applications built in react and angular where there is no physical back, like no actual server page to go back to just JavaScript, you have to code in what the back button means. Even though there’s no server calls to ask for a new page. New page. Most people still expect that forward and back will still go forward and back in standard navigation.
Sites like this it’s pretty clear that they just overwrite that with the last 20 calls to their own page, but the alternative is that single page applications would not be able to have forward or back functionality
Great I’ll just add a unique guid to each path that is ignored and returns to the same place. You show me a 10 foot fence I’ll show you an 11 foot ladder.
It’s a very “dumb” implementation of a generally useful feature. Browsers don’t keep track of how many times you’re redirected to the same site or try to consolidate the back-button list accordingly, but they certainly could. Wouldn’t be surprised if there was a plugin to this effect.
They actually do. To avoid infinite loops. If a URL redirects to the identical URL for more than ~5 times most browsers will refuse to load and show an error instead.
That’s why sites like this will generate new URLs with the same content.
I don’t understand why browsers support this “functionality”.
It’s not for this, of course. It’s because in the world of single page applications built in react and angular where there is no physical back, like no actual server page to go back to just JavaScript, you have to code in what the back button means. Even though there’s no server calls to ask for a new page. New page. Most people still expect that forward and back will still go forward and back in standard navigation.
Sites like this it’s pretty clear that they just overwrite that with the last 20 calls to their own page, but the alternative is that single page applications would not be able to have forward or back functionality
if(this == this.previous) continue;
Great I’ll just add a unique guid to each path that is ignored and returns to the same place. You show me a 10 foot fence I’ll show you an 11 foot ladder.
I mean, I get that. I was making a joke. But 12 ft fence? Load in sandbox and compare html. Your move.
13 ft ladder:
<span hidden><?= guid ?></span>14 ft fence: Diff in html. If less than 10 lines different, ban.
15 ft ladder:
<div hidden> <?= rand() ?> <?= rand() ?> <?= rand() ?> <?= rand() ?> <?= rand() ?> <?= rand() ?> <?= rand() ?> <?= rand() ?> <?= rand() ?> <?= rand() ?> <?= rand() ?> <?= rand() ?> <?= rand() ?> <?= rand() ?> <?= rand() ?> </div>Remove hidden elements and children before diff. 16 ft fence.
It’s a very “dumb” implementation of a generally useful feature. Browsers don’t keep track of how many times you’re redirected to the same site or try to consolidate the back-button list accordingly, but they certainly could. Wouldn’t be surprised if there was a plugin to this effect.
They actually do. To avoid infinite loops. If a URL redirects to the identical URL for more than ~5 times most browsers will refuse to load and show an error instead.
That’s why sites like this will generate new URLs with the same content.