Add hx-boost to header nav #164
Conversation
|
I may have to do a bit more research on this but my general opinion is pretty skeptical of this change. The gains seem a bit marginal since it still requests the full page but just replaces the body tag. Seems like added complexity for small if any gains unless I'm missing something. |
|
It's more of an improvement for UI/UX. It's not exactly measurable but links "feel" better to me when clicked. It's hard to explain. Definitely not necessary, just a small change I came across while working with htmx. |
|
The more I experiment with hx-boost, the less I like it. Closing this. |
|
What didn't you like about it? |
|
The main issue I ran into is the new page loading below the current page, instead of replacing it. This would usually happen if the link was populated from another htmx request. My solution was to add I also found that it does not carry over classes attached to the body. I have a page that doesn't extend I do really like how it feels. I haven't removed it from EB yet, if you want to check it out. Having the header stay consistent without "blinking" is really nice. I'm just not sure that is worth the potential risk of missing info outside of the body. |
|
The smoothness (e.g. no "blinking") isn't really noticeable unless you throttle the connection. So hx-boost seems to be more beneficial for users with slower connections. They are probably used to pages loading slower, though. |
This is a very small optimization using hx-boost.
Instead of navigating to a new page, internal links will use an AJAX request and replace the current page in place. The previous page is added to the browser's history and can still be navigated to using the back button. The docs mention the
<body>tag, but it actually replaces all html.