Make PREFETCH_DELAY configurable via Turbo.config.drive.prefetchDelay #1483
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Makes
PREFETCH_DELAYconfigurable viaTurbo.config.drive.prefetchDelay, addressing #1481.The current hardcoded 100ms delay can cause excessive prefetch requests on pages with many links (e.g., image galleries where cursor movement frequently hovers over multiple links).
Changes
prefetchDelaytoTurbo.config.drive(default: 100ms)PrefetchCacheto read the delay dynamically via a getter, so changes take effect immediatelyUsage
This follows the existing pattern used by Turbo.config.drive.progressBarDelay.