Title: Support pre-loading on hover · Issue #72080 · angular/angular · GitHub
Open Graph Title: Support pre-loading on hover · Issue #72080 · angular/angular
X Title: Support pre-loading on hover · Issue #72080 · angular/angular
Description: Which @angular/* package(s) are relevant/related to the feature request? router Description When a complex Angular app with lazy-loaded routes has many possible routes that are connected, it is hard to define a PreloadingStrategy that do...
Open Graph Description: Which @angular/* package(s) are relevant/related to the feature request? router Description When a complex Angular app with lazy-loaded routes has many possible routes that are connected, it is har...
X Description: Which @angular/* package(s) are relevant/related to the feature request? router Description When a complex Angular app with lazy-loaded routes has many possible routes that are connected, it is har...
Opengraph URL: https://github.com/angular/angular/issues/72080
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Support pre-loading on hover","articleBody":"### Which @angular/* package(s) are relevant/related to the feature request?\n\nrouter\n\n### Description\n\nWhen a complex Angular app with lazy-loaded routes has many possible routes that are connected, it is hard to define a `PreloadingStrategy` that does not pre-load too much while keeping the best User Experience / Performance.\n\nLet's say if the courrent route is page /b12 and you can possibly navigate to /b1, /b2, /b3, ... plus /a1, /c1, /d1, /e1... for the best User Experience you might want to preload all those routes, but not routes like /a2, /a3,\nThis is a lot of routes to pre-load, lots of network requests, and makes the `PreloadingStrategy` implementation bloated.\n\nThe best compromise I have seen in fwks so far is SvelteKit's [preload on hover](https://svelte.dev/docs/kit/link-options#data-sveltekit-preload-data) where there is nothing to setup for users. In the previous example, it would mean zero pre-loading until the user hovers on of the connected links.\n\nI am aware of the library `ngx-hover-preload` but it relies on either an Angular Module `HoverPreloadModule` or importing `LinkDirective` everywhere `routerLink` is used...\n\nWould you consider including in Angular's default router apis a way to preload on hover?\n\n### Proposed solution\n\nPropose a new `PreloadingStrategy` that supports preload on hover. \nIt would most likely involve a `Service` that is injected in the new `PreloadOnHoverStrategy` and optionally injected in `RouterLink`.\n\n### Alternatives considered\n\nWe can use `ngx-hover-preload` already, but not a fan of using modules in modern angular or repeating `LinkDirective` imports everywhere we are importing `RouterLink`.\n\nWe can also fork the `RouterLink` code and enhance it but that's **very far** from what we want, we highly value using Angular's default apis when we can.","author":{"url":"https://github.com/quentinderoubaix","@type":"Person","name":"quentinderoubaix"},"datePublished":"2026-11-18T08:48:07Z","url":"https://github.com/angular/angular/issues/72080"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:7248b078-bbf2-10d1-8303-eec77a954be6 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | C8A6:21BD98:29CDF68:35127F4:6B01DB66 |
| html-safe-nonce | 7f849e0e6fe67e2fb4eec03103db1dbd93ba9fbd460536bb5fbc1644337df886 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDOEE2OjIxQkQ5ODoyOUNERjY4OjM1MTI3RjQ6NkIwMURCNjYiLCJ2aXNpdG9yX2lkIjoiMTAyMzg2Nzc0MjEzNjE2MzE3NCIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 9caebdbaa8560fc771db9798609884f17ae3fb2402ce966c6d629a26f3c02b31 |
| hovercard-subject-tag | issue:6463398672 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/angular/angular/72080/issue_layout |
| twitter:image | https://opengraph.githubassets.com/5815184c0ec8f87c040a7211ab2a1691e1bc3ebbff76c9271cdea4a10135bf07/angular/angular/issues/72080 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/5815184c0ec8f87c040a7211ab2a1691e1bc3ebbff76c9271cdea4a10135bf07/angular/angular/issues/72080 |
| og:image:alt | Which @angular/* package(s) are relevant/related to the feature request? router Description When a complex Angular app with lazy-loaded routes has many possible routes that are connected, it is har... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | quentinderoubaix |
| hostname | github.com |
| expected-hostname | github.com |
| None | cc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c |
| turbo-cache-control | no-preview |
| go-import | github.com/angular/angular git https://github.com/angular/angular.git |
| octolytics-dimension-user_id | 139426 |
| octolytics-dimension-user_login | angular |
| octolytics-dimension-repository_id | 24195339 |
| octolytics-dimension-repository_nwo | angular/angular |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 24195339 |
| octolytics-dimension-repository_network_root_nwo | angular/angular |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 8c77c9e8439031ad54c75a250694842892f693e1 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width