René's URL Explorer Experiment


Title: Incremental hydration: a click that lands while a block is already hydrating is captured by event replay but never replayed · Issue #71296 · angular/angular · GitHub

Open Graph Title: Incremental hydration: a click that lands while a block is already hydrating is captured by event replay but never replayed · Issue #71296 · angular/angular

X Title: Incremental hydration: a click that lands while a block is already hydrating is captured by event replay but never replayed · Issue #71296 · angular/angular

Description: Which @angular/* package(s) are the source of the bug? core Is this a regression? No (same code on main today) Description With provideClientHydration(withIncrementalHydration(), withEventReplay()), a @defer (hydrate on viewport) block c...

Open Graph Description: Which @angular/* package(s) are the source of the bug? core Is this a regression? No (same code on main today) Description With provideClientHydration(withIncrementalHydration(), withEventReplay())...

X Description: Which @angular/* package(s) are the source of the bug? core Is this a regression? No (same code on main today) Description With provideClientHydration(withIncrementalHydration(), withEventReplay())...

Opengraph URL: https://github.com/angular/angular/issues/71296

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Incremental hydration: a click that lands while a block is already hydrating is captured by event replay but never replayed","articleBody":"### Which @angular/* package(s) are the source of the bug?\n\ncore\n\n### Is this a regression?\n\nNo (same code on `main` today)\n\n### Description\n\nWith `provideClientHydration(withIncrementalHydration(), withEventReplay())`, a `@defer (hydrate on viewport)` block containing a `routerLink` anchor loses any click that lands after the viewport trigger has started hydration but before it finishes. The jsaction contract captures the click and calls `preventDefault()`, so the browser does not navigate either. The event is queued for replay but never replayed, and once hydration completes the `jsaction` attribute is removed. The user clicks a link and nothing happens.\n\nThe same click works if it is the first thing to trigger hydration (before the viewport trigger fires), and after hydration has finished. Only the in-flight window is affected. That window is the lazy chunk fetch plus the block's first render, so it is a few ms on localhost, hundreds of ms on a mobile connection or a throttled CPU, and it opens exactly when the user has just scrolled the content into view.\n\nAny non-replay trigger has the same effect (`viewport`, `idle`, `timer`, `immediate`, `when`, a parent block hydrating), because the cause is in how a second hydration request is handled:\n\n1. `hydrateAndInvokeBlockListeners` (`packages/core/src/hydration/event_replay.ts`) pushes the event onto `EVENT_REPLAY_QUEUE` and calls `triggerHydrationFromBlockName(injector, blockName, replayFn)`.\n2. `triggerHydrationFromBlockName` (`packages/core/src/defer/triggering.ts`) sees the block in `dehydratedBlockRegistry.hydrating` and returns immediately, dropping `replayFn`.\n3. The in-flight hydration was started by `setViewportTriggers` with no replay function, so `triggerHydrationForBlockQueue` never drains the queue (`if (replayQueuedEventsFn) { replayQueuedEventsFn(hydrationQueue); }`).\n4. `cleanupHydratedDeferBlocks` removes `jsaction` / `ngb` from the block's elements. The event stays in the queue forever.\n\nA fix could be either of:\n\n- in the early-return path, attach the replay to the in-flight hydration, e.g. `blocksBeingHydrated.get(blockName).promise.then(() => replayQueuedEventsFn?.([blockName]))`, or\n- have `triggerHydrationForBlockQueue` always drain the shared queue for the blocks it hydrated, regardless of which trigger started it.\n\n### Please provide a link to a minimal reproduction of the bug\n\nhttps://github.com/stones/angular-incremental-hydration-click-replay (a fresh `ng new repro --ssr` with the files below, plus `probe.cjs`)\n\nChanges over the CLI scaffold:\n\n- `app.config.ts`: `provideClientHydration(withIncrementalHydration(), withEventReplay())`, `provideRouter(routes, withEnabledBlockingInitialNavigation())`.\n- `app.routes.ts`: `''` → `HomeComponent`, `'target'` → `TargetComponent` (renders \"TARGET PAGE\").\n- `app.routes.server.ts`: `{ path: '**', renderMode: RenderMode.Server }`.\n- `home.component.ts`: a 3000px spacer, then `@defer (hydrate on viewport) { \u003cslow-section /> } @placeholder { \u003cp>placeholder\u003c/p> }`.\n- `slow-section.component.ts`: standalone, imports `RouterLink`, template `\u003ca id=\"link\" routerLink=\"/target\" (click)=\"onClick()\">Go to target\u003c/a>`; `onClick` logs `handler ran`.\n\nSteps:\n\n```\nnpm install\nnpm run build\nNG_ALLOWED_HOSTS=localhost PORT=4017 node dist/repro/server/server.mjs\n```\n\n1. Open `http://localhost:4017/`. In DevTools, throttle the network to \"Slow 3G\" so the chunk fetch is long enough to click inside.\n2. Scroll the link into view. The IntersectionObserver fires and the `slow-section` chunk is requested.\n3. Click \"Go to target\" while the chunk is still loading.\n4. Nothing happens. The URL stays `/`, `handler ran` is never logged, and when the chunk arrives the anchor's `jsaction` attribute is gone.\n\nControls: `document.getElementById('link').click()` from the console before scrolling navigates (replay triggers hydration and is replayed). Clicking after the chunk has loaded navigates.\n\nAutomated: `node probe.cjs 5 50,300,800 dom,mouse 1000` runs the three scenarios in Playwright Chromium with 1000 ms of artificial latency on the lazy chunk. Results on 22.0.8:\n\n| Scenario | runs | navigated | handler ran | `jsaction` stripped after click |\n| --- | --- | --- | --- | --- |\n| click before the viewport trigger fires | 15 | 15 | 15 | 0 |\n| click during hydration (50 / 300 / 800 ms after scroll) | 40 | **0** | **0** | **40** |\n| click after hydration finished | 25 | 25 | 25 | 0 |\n\nBoth `element.click()` and a real `page.mouse.click()` behave the same.\n\n### Please provide the exception or error you saw\n\nNo error. The click is silently dropped.\n\n### Please provide the environment you discovered this bug in\n\n```\nAngular CLI: 22.0.9\nNode: 24.18.0\nPackage Manager: npm\nOS: win32 x64\n\n@angular/core 22.0.8 (also common, router, platform-browser, platform-server)\n@angular/ssr 22.0.9\n@angular/build 22.0.9\n```\n\n### Anything else?\n\nSeparate observation, possibly its own issue or docs gap: with the CLI default `provideRouter(routes)` (non-blocking initial navigation) the `hydrate on viewport` trigger in this app never registers. `withIncrementalHydration()`'s `APP_BOOTSTRAP_LISTENER` runs `runIncrementalHydrationBootstrap`, which is a no-op until `ɵɵenableIncrementalHydrationRuntime()` has run, and the compiler emits that call in the create block of the first template containing a hydrate block, which the router has not rendered when bootstrap finishes. The repro uses `withEnabledBlockingInitialNavigation()` to get past this.\n","author":{"url":"https://github.com/stones","@type":"Person","name":"stones"},"datePublished":"2026-10-11T06:46:49Z","url":"https://github.com/angular/angular/issues/71296"}

react-profiling0
react-import-mapreact,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-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:83e81dbe-8eba-4c27-68ee-eba4b797f397
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idC8C4:27E5CD:357906F:4467FED:6B01DB67
html-safe-nonce6c792d942b0aaceb5087bfb60ce6b7f1016c49c1152f39386f03f1cf290cb8d2
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDOEM0OjI3RTVDRDozNTc5MDZGOjQ0NjdGRUQ6NkIwMURCNjciLCJ2aXNpdG9yX2lkIjoiNzExNjM0NjI4MjQ5ODcxMDM3NiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9
visitor-hmac8658178301730dffcf885cdceb7dd2449253912f023bbdd39cef2cc71a69bae7
hovercard-subject-tagissue:5798721656
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/angular/angular/71296/issue_layout
twitter:imagehttps://opengraph.githubassets.com/2e59dd4d5ea2fe5876c260a2608dc525d67b292fc41d800cfa5a864b98c395b5/angular/angular/issues/71296
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/2e59dd4d5ea2fe5876c260a2608dc525d67b292fc41d800cfa5a864b98c395b5/angular/angular/issues/71296
og:image:altWhich @angular/* package(s) are the source of the bug? core Is this a regression? No (same code on main today) Description With provideClientHydration(withIncrementalHydration(), withEventReplay())...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernamestones
hostnamegithub.com
expected-hostnamegithub.com
Nonecc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c
turbo-cache-controlno-preview
go-importgithub.com/angular/angular git https://github.com/angular/angular.git
octolytics-dimension-user_id139426
octolytics-dimension-user_loginangular
octolytics-dimension-repository_id24195339
octolytics-dimension-repository_nwoangular/angular
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id24195339
octolytics-dimension-repository_network_root_nwoangular/angular
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release8c77c9e8439031ad54c75a250694842892f693e1
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/angular/angular/issues/71296#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fangular%2Fangular%2Fissues%2F71296
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fangular%2Fangular%2Fissues%2F71296
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=angular%2Fangular
Reloadhttps://github.com/angular/angular/issues/71296
Reloadhttps://github.com/angular/angular/issues/71296
Reloadhttps://github.com/angular/angular/issues/71296
angularhttps://github.com/angular
angularhttps://github.com/angular/angular
Codehttps://github.com/angular/angular
Issues835 (835)https://github.com/angular/angular/issues
Pull requests142 (142)https://github.com/angular/angular/pulls
Discussionshttps://github.com/angular/angular/discussions
Actionshttps://github.com/angular/angular/actions
Projectshttps://github.com/angular/angular/projects
Security and quality40 (40)https://github.com/angular/angular/security
Insightshttps://github.com/angular/angular/insights
https://github.com/angular/angular
New issuehttps://github.com/login?return_to=https://github.com/angular/angular/issues/71296
New issuehttps://github.com/login?return_to=https://github.com/angular/angular/issues/71296
#72127https://github.com/angular/angular/pull/72127
Incremental hydration: a click that lands while a block is already hydrating is captured by event replay but never replayedhttps://github.com/angular/angular/issues/71296#top
#72127https://github.com/angular/angular/pull/72127
area: coreIssues related to the framework runtimehttps://github.com/angular/angular/issues?q=state%3Aopen%20label%3A%22area%3A%20core%22
needsTriagehttps://github.com/angular/angular/milestone/83
https://github.com/stones
stoneshttps://github.com/stones
on Oct 11, 2026https://github.com/angular/angular/issues/71296#issue-5798721656
https://github.com/stones/angular-incremental-hydration-click-replayhttps://github.com/stones/angular-incremental-hydration-click-replay
angular-robothttps://github.com/apps/angular-robot
area: coreIssues related to the framework runtimehttps://github.com/angular/angular/issues?q=state%3Aopen%20label%3A%22area%3A%20core%22
on Oct 11, 2026https://github.com/angular/angular/issues/71296#event-32974444863
angular-robothttps://github.com/apps/angular-robot
needsTriagehttps://github.com/angular/angular/milestone/83
on Oct 11, 2026https://github.com/angular/angular/issues/71296#event-32974445418
alexemorrishttps://github.com/alexemorris
on Nov 19, 2026https://github.com/angular/angular/issues/71296#event-36690058098
fix(core): drain queued replay events during defer hydrationhttps://github.com/alexemorris/angular/commit/9f239d2d49b4ac7f17aa559c5bc7119cee31ff53
https://docs.github.com/articles/closing-issues-via-commit-messages
9f239d2https://github.com/alexemorris/angular/commit/9f239d2d49b4ac7f17aa559c5bc7119cee31ff53
fix(core): drain queued replay events during defer hydrationhttps://github.com/alexemorris/angular/commit/775fe81a813da7c19b95aadc636492c71ecfda19
https://docs.github.com/articles/closing-issues-via-commit-messages
775fe81https://github.com/alexemorris/angular/commit/775fe81a813da7c19b95aadc636492c71ecfda19
fix(core): drain queued replay events during defer hydrationhttps://github.com/alexemorris/angular/commit/303f21ee53bcd7f45999ff20bd0722326cc00bb8
https://docs.github.com/articles/closing-issues-via-commit-messages
303f21ehttps://github.com/alexemorris/angular/commit/303f21ee53bcd7f45999ff20bd0722326cc00bb8
Sign up for freehttps://github.com/signup?return_to=https://github.com/angular/angular/issues/71296
Sign in to commenthttps://github.com/login?return_to=https://github.com/angular/angular/issues/71296
area: coreIssues related to the framework runtimehttps://github.com/angular/angular/issues?q=state%3Aopen%20label%3A%22area%3A%20core%22
needsTriageNo due datehttps://github.com/angular/angular/milestone/83
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.