Framework7 Router and Request Library: Automatic Request Cancellation on Concurrent Navigation?

Integration Boundary

Framework7's Router handles asynchronous route resolution through dynamic imports and template loading, while the Request Library (f7.request) manages XHR and fetch calls independently. The two subsystems operate without a shared cancellation protocol.

Goal and Constraints

The objective is to determine whether the framework provides any built-in mechanism that aborts in-flight Request Library calls when a new navigation begins before previous requests complete. Current documentation and source inspection suggest no automatic linkage exists: Router navigation guards (beforeEnter, beforeLeave) do not implicitly signal the Request Library, and no global request registry is exposed for bulk cancellation. Developers must manually wire AbortController instances into route guards, a pattern the framework neither enforces nor simplifies.

Version assumptions: Framework7 v7 and v8 core (vanilla) are the primary targets; Vue, React, and Svelte bindings may introduce additional lifecycle differences that affect when component-mounted requests fire relative to navigation commits. Browser connection limits (six concurrent connections per host) can amplify latency when stale requests occupy slots needed for the active route's critical data fetches.

Open Questions

1. Does any Framework7 release (v7.x, v8.x, or recent patches) introduce an internal hook or option that couples Router navigation events to Request Library abort behavior?
2. If no such hook exists, what is the recommended pattern for associating an AbortController with a specific route instance so that rapid repeated navigations to the same route (with different query parameters) reliably cancel only the superseded requests?
3. Are there documented differences in cancellation semantics between the vanilla core and the framework-specific wrappers that would affect a portable cancellation strategy?