Replies: 3 comments 10 replies
-
|
Have you tried? That post was about alpine v2. Alpine v3 is different, if the framework patches the Dom by adding/removing elements on a page where Alpine has already been started, Alpine should see the changes and initialise the new elements. |
Beta Was this translation helpful? Give feedback.
10 replies
-
|
Working on this in #4714 and made some progress you might be interested in |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Following this thread as I'm battling this issue right now. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When enabling Enhanced navigation in Blazor clicking an anchor results in the framework intercepting the request and performing a fetch request instead. Blazor then patches the response content into the page's DOM. I'd say this would cause problems since
Alpine.start()only runs on the first full page load. It is possible to react when Blazor has patched the DOM:I've read this thread regarding liveview and there's a lot of talk about using
Alpine.discoverUninitializedComponentsbut I really didn't find any conclusive answer.Beta Was this translation helpful? Give feedback.
All reactions