# htmx-general
- m
mysterious-toddler-20573
03/09/2021, 10:00 PMthat's my guess - g
gentle-dream-18175
03/09/2021, 10:00 PMright. so i guess my thought was, it would do ID matching first and then the default innerHTML swap - m
mysterious-toddler-20573
03/09/2021, 10:01 PMyou definitely want an outerHTML swap there - s
salmon-xylophone-28580
03/10/2021, 8:41 AMI still think "outerHTML" should be the default. - g
glamorous-honey-42686
03/10/2021, 9:19 AMIf I use hx-boost, and the response contains a HX-Refresh header. Isn't it supposed to refresh the page I was navigating to? Instead of the page I was on when clicking the link that was boosted - t
tall-dinner-62086
03/10/2021, 10:29 AMWhy would you refresh a page you've just loaded? - g
glamorous-honey-42686
03/10/2021, 10:31 AMIf we discover a mismatch between what version of the app had when we loaded the original page that contains assets etc and the response we get - t
tall-dinner-62086
03/10/2021, 10:31 AMI see - m
mysterious-toddler-20573
03/10/2021, 10:32 AMYes that sounds like a bug - g
glamorous-honey-42686
03/10/2021, 10:32 AMOtherwise people that have the app open will never receive updates to assets unless they reload the page completely. But we handle it differently instead. We prevent boosting if we discover a new version - g
glamorous-honey-42686
03/10/2021, 10:32 AMI think refreshing would be a problem if you for instance submit a form - t
tall-dinner-62086
03/10/2021, 10:32 AMTo "prevent boosting" wouldn't you reply with a HX-Redirect instead? - m
mysterious-toddler-20573
03/10/2021, 10:34 AMHx-refresh should execute after hx-push if possible it seems like - g
glamorous-honey-42686
03/10/2021, 10:34 AMWe thought about redirect... but that also would be a problem with forms etc... So instead we check for new version in afterswap and then change hx-boost to false - t
tall-dinner-62086
03/10/2021, 10:35 AMWhat do you want to do when an out-of-date form is submitted? - m
mysterious-toddler-20573
03/10/2021, 10:35 AMYou need to write a book on advanced htmx! - g
glamorous-honey-42686
03/10/2021, 10:36 AMwe process the form as usual, but the next request will not be boosted - g
glamorous-honey-42686
03/10/2021, 10:37 AMHeh.. We haven't really rolled out htmx in production yet... This is just preparing for our first rollout - t
tall-dinner-62086
03/10/2021, 10:38 AMSorry ya lost me. You un-boost when you detect a change, why would you need HX-Refresh on a boosted request after that? - g
glamorous-honey-42686
03/10/2021, 10:39 AMSorry... I was probably a bit unclear. We don't use HX-Refresh anymore. We noticed the issues since I posted the question and went with the un-boosting instead - t
tall-dinner-62086
03/10/2021, 10:39 AMoooh - t
tall-dinner-62086
03/10/2021, 10:43 AMSo what handling refresh after push would do is basically a pre-emptive unboost. Which just sounds a lot like a HX-Redirect, but also doing it the other way around results in just a refresh, no push. - m
mysterious-toddler-20573
03/10/2021, 10:46 AMAnother option would be to submit the app version on requests, maybe as a header and show a refresh header div when it doesn’t match the server version. Some apps I use (like asana) do that - t
tall-dinner-62086
03/10/2021, 10:47 AMheck discord does that on the browser, you get a little green download icon on the top when it's time to update - t
tall-dinner-62086
03/10/2021, 10:48 AMHowever, if you have any kind of breaking change, or an urgent security fix, you probably don't want to rely on the user choosing when to update - m
mysterious-toddler-20573
03/10/2021, 10:49 AMYou could trigger a custom event w a set timeout... - t
tall-dinner-62086
03/10/2021, 10:50 AMTrue - t
tall-dinner-62086
03/10/2021, 10:50 AMBut considering you can't handle the HX-Push after the HX-Refresh, it would make sense to have the push be handled first. Even if all it does is emulate a redirect. - m
mysterious-toddler-20573
03/10/2021, 10:52 AMon appUpdate wait 1ms then call window.location.reload(true)