Voxera75913dProbably created before client side routing was a thing.
I mean, its not a consumer product. Its something you sell to a boss or a manager, what do they care about usability for the personnel ;)
Upgrading it to modern technology would make it more expensive compared to just upgrade the sales pitch :P
Over the years I've had some really batshit asks for what history states should do. I've also found the vast majority of users for whatever reason want a clickable for everything, the back button is something they never use.
I mean, it's the default for my applications, but I also gets complaints about it, especially when I bind it to modality for data entry safety purposes 🤷♀️
That said, if you don't have routing and history states, it's not a spa by definition.
I’ve developed with both Angular and react and Angular’s router is very good as it handles basic navigation, plus you can intercept requests which is a handy feature
However react’s router is garbage and a nightmare to work with and honestly wouldn’t recommend it