Implement browser history API based navigation, preventing page reloads between routings

[mercihabam]

#1144

Checklist:

• The sidebar item's active state updates when navigating
• Ensure handlers for refresh links are applied so the browser doesn’t reload on click
• Sorting and filtering work
• Fix combined folder content not being loaded upon navigation
• Can display flagged contents
• Cronjob to reload active folder's content in the background
• Refresh the list during navigation; at least in the background.
• FIX: Navigating to a route, the data from a previous route gets fetched.
• Fix unit tests relative to the js files output
• When clicking on a message link while contents are still being fetched in the background, the requests should be aborted so the navigation is performed faster (Aborting the requests on the client doesn't help because, once the requests are sent, the server processes them synchronously, blocking other eventual requests. A solution could be processing the requests server-side asynchronously.)
• Can requests be processed asynchronously? Let's keep track of this here: Message content requests are processed synchronously, resulting in a frozen screen when the user clicks on a message row. #1279

[marclaporte]

@jacob-js A test is failing.

[mercihabam]

@jacob-js A test is failing.

Locally the same test is succeeding, not sure why in the CI it is failing. @kroky could you have some insights?
Here is what I have when I execute that test:

LOGIN TESTS
 - loading site
 - logging in
 - finding element by name username
 - finding element by name password
 - finding element by selector input[value=Login]
 - waiting for page by tag name: body ...
 - finding element by class sys_messages
bad_login_values PASSED
 - loading site
 - logging in
 - finding element by name username
 - finding element by name password
 - finding element by selector input[value=Login]
 - waiting for page by tag name: body ...
 - finding element by class login_form
missing_password PASSED
 - loading site
 - logging in
 - finding element by name username
 - finding element by name password
 - finding element by selector input[value=Login]
 - waiting for page by tag name: body ...
 - finding element by class login_form
missing_username PASSED
 - loading site
 - logging in
 - finding element by name username
 - finding element by name password
 - finding element by selector input[value=Login]
 - waiting for page by tag name: body ...
 - finding element by class login_form
missing_username_and_password PASSED
 - loading site
 - finding element by name hm_page_key
 - logging in
 - finding element by name username
 - finding element by name password
 - finding element by selector input[value=Login]
 - waiting for page by tag name: body ...
 - finding element by class login_form
bad_login_key PASSED
 - loading site
 - logging in
 - finding element by name username
 - finding element by name password
 - finding element by selector input[value=Login]
 - waiting for page by class name: main_menu ...
 - finding element by class content_title
good_login PASSED
 - logging out
 - waiting for page by tag name: body ...
 - finding element by class sys_messages
good_logout PASSED

7 of 7 PASSED

[kroky]

Changes look good. I am also puzzled by the failing CI test - it is either an unsaved change that is triggering the password dialog on logout or somehow sys_messages become inaccessible for selenium. I think that needs to be debugged more in the pipeline itself, since it can't be reproduced locally. I'd try swapping logout with logout_no_save first.

[mercihabam]

Changes look good. I am also puzzled by the failing CI test - it is either an unsaved change that is triggering the password dialog on logout or somehow sys_messages become inaccessible for selenium. I think that needs to be debugged more in the pipeline itself, since it can't be reproduced locally. I'd try swapping logout with logout_no_save first.

The incoherence in the test results was due to different modes used in the test environment. The CI doesn't run in debug mode, whereas locally, the app is executed in debug mode.

[mercihabam]

@kroky could you look at the changes one more time please?