4 ms·
Really interesting concept, but I think something is very wrong with whatever it is doing to (intentionally?) highjack browser histories/navigation on every pag
by drusepth 3y ago
Really interesting concept, but I think something is very wrong with whatever it is doing to (intentionally?) highjack browser histories/navigation on every page.
For example, if I just click "Refried beans" on the homepage, then click the recipe for "Refried beans" from the ingredients list on that page... it takes pressing Back on the browser FIVE times before I'm finally back at the homepage. And, interestingly, at no point during this process do I actually go back to the actually-previous page (where you land after clicking "refried beans" on the homepage) -- I just stay on the current page as the URL changes every time and then eventually make it all the way back to the homepage with nothing in-between.
- Maxion 3y ago> For example, if I just click "Refried beans" on the homepage, then click the recipe for "Refried beans" from the ingredients list on that page... it takes pressing Back on the browser FIVE times before I'm finally back at the homepage. I must be getting old. There's no hijacking going on here, the page uses URL params, and probably JS to decode them.
- worewood 3y agoSo I'd say that the page must hijack the history to not pollute it with navigations that from the user perspective, aren't navigations.
- explaininjs 3y agoURL params have (almost) nothing to do with history hijacking. That’s all the history.pushStare and replaceState API’s.