Visiting the current URL doesn't reload the turbo frame

I have a link that points to the current URL (acting as a reload button), and it targets a turbo frame.

Clicking on the link the first time works; the frame is reloaded, and the src value of the frame is updated. Clicking on the link the second time doesn’t work, there are no HTTP requests being made, and the frame is not reloaded.

I’m assuming it’s because Turbo doesn’t detect that src has changed, since it’s the same link. However, this is not how regular links behave, you can always visit the current page, so I think it would make sense for Turbo to have the same behaviour.

Possibly related to https://github.com/hotwired/turbo/issues/249#issuecomment-830124904 and https://github.com/hotwired/turbo/issues/202.

[Bramjetten]

I don’t understand why reloading the current URL is not allowed. This behaviour is counterintuitive to me. Adding a timestamp works as a temporary workaround. Reloading a frame can be useful to easily reset a frame’s initial state.

[janko]

Thanks for the reply. We initially used the approach of clearing the src first, but then we switched to adding a timestamp to the URL.

However, I don’t understand in which scenarios is this kind of caching useful. Personally, I would expect caching to only happen based on caching-related HTTP response headers.

I actually feel like this unexpected behaviour is coming from Turbo Frames possibly being designed to only watch for src changes on the frame, considering that navigateFrame only changes the frame’s src. In this case it’s obvious there is a limitation of not detecting reloads.