Turbo Drive 2.0: Should a Global Timeout Configuration Be Added?
Developers using Turbo Drive often need to limit how long a page visit can wait for a server response, especially when dealing with unreliable backends or long‑running endpoints. The current implementation relies on the Fetch API and provides no default timeout; a visit proceeds until the network layer signals failure or the server replies. To impose a limit