Skip to content
This repository has been archived by the owner on Jul 28, 2018. It is now read-only.

Don't clone data-turbolinks-permanent and :keep nodes #479

Merged
merged 1 commit into from
Mar 7, 2015

Conversation

Thibaut
Copy link
Collaborator

@Thibaut Thibaut commented Mar 7, 2015

Fix #477

Tests pass in latest Firefox, Chrome, Safari and IE10.

cc @reed @dhh @kristianpd @jtomaszewski

dhh added a commit that referenced this pull request Mar 7, 2015
Don't clone data-turbolinks-permanent and :keep nodes
@dhh dhh merged commit 6f3bc73 into turbolinks:master Mar 7, 2015
@Thibaut Thibaut deleted the transfer-node branch March 8, 2015 00:14
@reed
Copy link
Collaborator

reed commented Mar 9, 2015

@Thibaut I just discovered that due to this change, permanent nodes disappear from cached pages. I hit the back button and all the sections with data-turbolinks-permanent were gone. Thoughts?

@jtomaszewski
Copy link

Yeah, I think I noticed the same behaviour at my app.

@Thibaut
Copy link
Collaborator Author

Thibaut commented Mar 9, 2015

@reed @jtomaszewski I noticed some weird stuff around back/forward navigation too. I'll PR tests and a fix by the end of the week.

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

Successfully merging this pull request may close these issues.

Don't necessarily clone nodes, but move them, when using data-turbolinks-permanent
4 participants