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

Twinspark doesn't appear to play well with other component libraries #44

Open
coreagile opened this issue Jun 18, 2024 · 2 comments
Open

Comments

@coreagile
Copy link

So, I've got an app that I'm trying to gradually replace all its front end logic (using lit html) with twinspark. Sadly, though, when I introduce the library onto a page with lit html components, it causes very strange behavior. Namely, when I navigate away from the dynamic page and I navigate back, all the components duplicate.

When I remove the twinspark library the component duplication doesn't happen any more.

Do you have any idea why that might happen?

Thanks for any insights you might have!

@coreagile
Copy link
Author

coreagile commented Jun 18, 2024

Interesting note: when I set data-history="0" the duplication goes away.

Edit: Nevermind. It doesn't actually help. The only thing that seems to help is removing twinspark altogether.

@piranha
Copy link
Owner

piranha commented Aug 21, 2024

Well it certainly feels like history management is conflicting with something... If you could provide a minimal example, I'd love to take a look, because I've had similar problem once, but couldn't reproduce.

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

2 participants