Skip to content
This repository has been archived by the owner on Sep 25, 2021. It is now read-only.

[Question] "Standard" Turbo Visit inside Visitable #180

Open
krisdigital opened this issue Feb 7, 2021 · 0 comments
Open

[Question] "Standard" Turbo Visit inside Visitable #180

krisdigital opened this issue Feb 7, 2021 · 0 comments

Comments

@krisdigital
Copy link

krisdigital commented Feb 7, 2021

Could not figure it out: Is there a possibility to visit the same Visitable with a different URL?

You may already have answered the question here #127 but wanted to be sure before cooking up a custom solution..

I have a tab like navigation similar to the one in the Twitter app on my turbo powered web app:
image

The closest I could get is by visiting a new Visitable, then waiting for the request to finish, and only then replace the last ViewController with the new one. But there is still a flicker while pushing it onto the navigationController which is a little trashy..

The advance action - using the screenshot of the webview while pushing a new one - works great, but replacing is somewhat different than using Turbolinks on a website, where the page stays until the response loaded and is then replaced.

Or can I use the "normal" Turbolinks behaviour for these cases? As far as I could see the native turbo adapter overrides the normal Turbo behaviour..

Thank's!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant