Web UI navigation and drawbacks of SPA

[dima-ser]

I must admit, I find myself constantly hitting the "Back" button in my browser to get back to previous page and get taken out of the site completely.
This may be too big of change, but I am honestly not a big fan of the decision to use Single-Page Application Architecture for the web interface. It becomes very apparent when, for example, you view DCHP scope and it loads a long page and if you want to go back to the list of all DHCP scopes, you can't just hit "Back" in your browser. Instead, you have to scroll all the way down to the end of the page and click the Cancel button. I think everyone can agree this is not ideal.
It's not the end of the world, but it's a slight annoyance is an otherwise excellent product. It's probably too big of a lift to convert away from SPA, but I figured I'd leave this here. Perhaps there is another way to solve these navigation issues within SPA.

[ShreyasZare]

Thanks for the post. There is already plan to add support for this using URL bookmarks so it works with Back button. But this is kind of low priority feature and will take time to implement since there are too many core features being prioritized. I am trying to add a few UI features in between a couple of releases to keep up with the requests though so kind of depends on how time permits.

That said, the app is SPA since it allows the page to stay with maintaining state of various views to minimize the number of time the same data is pulled from the backend and also makes it easier for user to switch between multiple views while debugging things. So, it has some good pros too.

DHCP UI will get totally changed later when the DHCPv6 and major refactoring of existing DHCP server is planned. So, its not being changed currently.