News for hackers. Stuff that matters.

A comment on Why I Tend Not to Use Content Negotiation. Parent comment

Re:Why I Tend Not to Use Content Negotiation by alex_smart on Monday November 20, 2023 @12:32AM (#38342792)
> But that was too ugly for URLs, so modern websites now use browser history APIs just so they can remove 3 characters from the URL and do stuff like

Would back/forward buttons continue to work if we decided not use browser history APIs?

[ Parent | on HN ]
Re:Why I Tend Not to Use Content Negotiation by quectophoton on Monday November 20, 2023 @01:14AM (#38343248)
Yes, and a quick test with Mithril.js confirms it.

I could try with something like React, but that's too much for a quick test.

[ Parent | on HN ]
Re:Why I Tend Not to Use Content Negotiation by mewpmewp2 on Monday November 20, 2023 @07:21AM (#38346959)
Mithril.js also probably uses the history API?

.replaceState() will replace current url without putting it in the history, so back won't work, while .pushState() does.

[ Parent | on HN ]
Re:Why I Tend Not to Use Content Negotiation by PH95VuimJjqBqy on Monday November 20, 2023 @02:59PM (#38353677)
The other poster is wrong, the entire reason the history API exists is specifically because when these SPA frameworks first came onto the scene one of the things that was broken was history.

So they invented the history API's so SPA's could stop breaking some of the user expectations they were breaking.

[ Parent | on HN ]