Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Turbolinks 5 compatibility #72

Open
sdhull opened this issue Aug 13, 2016 · 8 comments
Open

Turbolinks 5 compatibility #72

sdhull opened this issue Aug 13, 2016 · 8 comments

Comments

@sdhull
Copy link

sdhull commented Aug 13, 2016

First off, thanks for building this excellent resource! It has saved me some time.

Second, as you probably know, the new version of Turbolinks uses completely different events. So none of the solutions you have here are applicable for Turbolinks 5.

I've reworked the Twitter & FB solutions to work with Turbolinks 5. Maybe start a turbolinks-5 branch or something that I could submit PRs to? Or a separate repo for turbolinks 5?

@andyrsmith
Copy link

I would vote for starting a new repo so that people using the old version of turbolinks still have this as a resources.

Do you have your twitter & FB solutions up so I can look at them?

@sdhull
Copy link
Author

sdhull commented Aug 22, 2016

@andyrsmith Uhh yeah here you go:
facebook
twitter

@borisrorsvort
Copy link

@sdhull Would you have an example with loading a timeline widget? Also does it work with the back button.
For the only I manage to make it work is to disable turbolinks cache for these pages

@sdhull
Copy link
Author

sdhull commented Mar 7, 2017

@borisrorsvort not sure what you mean by "a timeline widget"? Is there something specific you're trying to make work?

It's been on my to-do list to do something about this, either open a PR on this repo or start a new repo. I'm inclined to open a PR here as long as @reed is still interested in reviewing & accepting PRs here.

@reed
Copy link
Owner

reed commented Mar 7, 2017

I'll review anything you submit.

@borisrorsvort
Copy link

@reed @andyrsmith can we have another branch for T5 and at some point make the switch when T5 will be mainstream. Second option would be to create another turbolinks-classic-compatibility with this content to follow the official Turbolinks convention.

@sdhull Main problems I have now with twitter timelines (https://dev.twitter.com/web/javascript/creating-widgets#create-timeline) are with the back button behaviour, as it leaves an empty iframe.

@sdhull
Copy link
Author

sdhull commented Mar 7, 2017

@borisrorsvort ok when I get home from work today I'll check out the timelines widget.

As for a T5 branch, I'm thinking instead that since this is a gh pages project, we should instead perhaps just add a section for turbolinks 5, or something like that. Add it 5/4 to the navigation.

@borisrorsvort
Copy link

@sdhull I added your solutions in the pr #75

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

No branches or pull requests

4 participants