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

Frames: Abort prior requests during navigation #418

Merged

Conversation

seanpdoyle
Copy link
Contributor

Closes #417


If there is an unresolved FetchRequest in-flight when navigating a
Turbo Frame, abort its underlying AbortController instance.

Closes hotwired#417

---

If there is an unresolved `FetchRequest` in-flight when navigating a
Turbo Frame, [abort][] its underlying [AbortController][] instance.

[abort]: https://developer.mozilla.org/en-US/docs/Web/API/AbortController/abort
[AbortController]: https://developer.mozilla.org/en-US/docs/Web/API/AbortController
@seanpdoyle seanpdoyle force-pushed the frame-cancel-pending-navigation-requests branch from 3e4beca to 7a7d836 Compare October 4, 2021 17:42
@dhh dhh merged commit 4e3d05d into hotwired:main Oct 4, 2021
@seanpdoyle seanpdoyle deleted the frame-cancel-pending-navigation-requests branch October 4, 2021 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Setting TurboFrameElement.src twice in quick succession can show wrong source
3 participants