-
Notifications
You must be signed in to change notification settings - Fork 431
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
hotwire-example-pagination
not works with 7.2.5
#873
Comments
If I remove the line https://github.com/hotwired/turbo/blob/main/src/core/frames/frame_controller.ts#L180, it works fine. |
@seb-jean thank you for opening this issue!
Does the new URL reflect the path of the lazily-loaded If you're able, could you try to experiment with the changes made in #430? That PR re-arranges some of the frame promotion logic, and might help resolve the underlying issue. |
I put the HTML code if it can help for the issue: <turbo-frame id="notifications-page-1" target="_top">
<div class="item">[...]</div>
<div class="item">[...]</div>
<div class="item">[...]</div>
<div class="item">[...]</div>
<div class="item">[...]</div>
<div class="item">[...]</div>
<div class="item">[...]</div>
<turbo-frame id="notifications-page-2" class="group block py-6" data-turbo-action="replace" src="/notifications?page=2" loading="lazy" data-controller="element" data-action="turbo:frame-render->element#replaceWithChildren">
<a class="hidden group-last-of-type:flex justify-center pointer-events-none" tabindex="-1" aria-hidden="true" rel="next" href="/notifications?page=2">
<svg>[...]</svg>
</a>
</turbo-frame>
</turbo-frame> |
<turbo-frame id="notifications-page-2" class="group block py-6" data-turbo-action="replace" ...> Rendering that The intention behind that example code is to update the URL's |
Ok, it works perfectly. |
@seb-jean that's great news! Could you close this issue? |
Thx @seanpdoyle |
Hi,
I updated Turbo from
7.2.4
to7.2.5
and the hotwire-example-pagination demo no longer works:The url is modified in the browser’s path.
The text was updated successfully, but these errors were encountered: