I ran into a case where I was trying to apply some logic after page transitions where the user's session might have changed, and I hit this issue where 95% of the time I could hook into "turbo:load" events but 5% of the time (and depending on which page the user was on, and what the controller response was doing) the session change resulted in mrujs doing a page morph buuuuut there's no events that gets fired when that happens so there's nothing to listen for. So an event here would be really helpful.
I wasn't sure about the naming; it somewhat breaks from the convention of "ajax:<eventname>", but it feels like this event announcing an mrujs/morphdom update isn't related to ajax? As always, naming things is hard :man_shrugging:
Status
Related Issue(s)
-
Additional Notes
I ran into a case where I was trying to apply some logic after page transitions where the user's session might have changed, and I hit this issue where 95% of the time I could hook into
"turbo:load"
events but 5% of the time (and depending on which page the user was on, and what the controller response was doing) the session change resulted inmrujs
doing a page morph buuuuut there's no events that gets fired when that happens so there's nothing to listen for. So an event here would be really helpful.I wasn't sure about the naming; it somewhat breaks from the convention of
"ajax:<eventname>"
, but it feels like this event announcing an mrujs/morphdom update isn't related to ajax? As always, naming things is hard :man_shrugging: