Using hx-boost abort previous requests

[akBeater]

Hello,
i hope this is the right place for my question.

I have a simpel website with a sidebar which functions as navigation.
Therefore the links have hx-boost="true". The remaining space of the page shows the page itself.
I now have the following Problem:

• I navigate to page "/page1" by clicking on a link on the sidebar (boosted)
• In "/page1" I click on a button, which issues a long request, which refreshes the page, when its finished
• If I navigate to "/page2" in the meantime, the request is still ongoing. So while I'm on "/page2" the website refreshes because the other request finishes.

Another example is:

• I navigate to "/page3" which takes very long
• because its loading too slow, I navigate to "/page4" and do other things
• While I'm on "/page4" suddenly "/page3" gets loaded, because the request finishes

My question is how can I prevent this?
I think I have to abort all pending requests when I'm navigating with hx-boost, but is there a simpel way?

Thanks :)

[Telroshan]

Hey,
You might want to look into hx-sync which could help here!
You could for example synchronize on the body itself for boosted navigation, with a replace strategy so that /page4 would override the /page3 request
As for your first example, you could also synchronize on the body but it could start getting messy if you have multiple elements doing that. If you have a bunch of page-specific requests that should be able to coexist together but all be aborted when changing page, you might want to simply revert to hard page loads and let the browser do its job!

Hope this helps!

[akBeater]

Hey,
thanks for the fast reply!

I will look into hx-sync. Maybe I can create something in a simple matter. I will post an update here.
As a (temporary) solution, I actually disabled hx-boost and let it hard reload as you mentioned. It works and this application is relative small, so this is no problem.