Title: Hydration: projected content is missing when `
Open Graph Title: Hydration: projected content is missing when `
X Title: Hydration: projected content is missing when `
Description: Which @angular/* package(s) are the source of the bug? core Is this a regression? No It reproduces on 20.3.35, 21.2.26 and 22.3.0 (the current latest), in development and production builds. Description With hydration enabled, content pro...
Open Graph Description: Which @angular/* package(s) are the source of the bug? core Is this a regression? No It reproduces on 20.3.35, 21.2.26 and 22.3.0 (the current latest), in development and production builds. Descrip...
X Description: Which @angular/* package(s) are the source of the bug? core Is this a regression? No It reproduces on 20.3.35, 21.2.26 and 22.3.0 (the current latest), in development and production builds. Descrip...
Opengraph URL: https://github.com/angular/angular/issues/72132
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Hydration: projected content is missing when `\u003cng-content>` sits inside an element that was not projected on the server","articleBody":"### Which @angular/* package(s) are the source of the bug?\n\ncore\n\n### Is this a regression?\n\nNo\n\nIt reproduces on 20.3.35, 21.2.26 and 22.3.0 (the current `latest`), in development and production builds.\n\n### Description\n\nWith hydration enabled, content projected through an `\u003cng-content>` slot is lost when all of these hold:\n\n1. A component template (`WrapperComponent`) places an `\u003cng-content />` inside an element, for example `\u003cdiv>\u003cng-content />\u003c/div>`, in the content of another component (`\u003capp-container>`).\n2. The other component (`ContainerComponent`) does not render its own `\u003cng-content>` on the server, for example because the slot sits inside an `@if` that is `false`.\n3. The condition becomes `true` after hydration.\n\nThe server render succeeds, hydration reports no error, and the server DOM is reused. But once the container opens, it shows an empty `\u003cdiv>`: the projected text is missing. It stays missing after closing and opening the container again. Nothing is logged in the console.\n\nWithout `provideClientHydration()`, or with the condition already `true` on the server, the text is there.\n\nResults in headless Chromium (Chrome for Testing 156). The development and production builds give the same results:\n\n| Template inside `\u003capp-container [open]=\"open()\">` | `open` on the server | `provideClientHydration()` | `\u003capp-container>` after opening |\n| --- | --- | --- | --- |\n| `\u003cdiv>\u003cng-content />\u003c/div>` | `false` | yes | `\u003cdiv>\u003c/div>` |\n| `\u003cdiv>\u003cng-content />\u003c/div>` | `false` | no | `\u003cdiv>projected text\u003c/div>` |\n| `\u003cdiv>\u003cng-content />\u003c/div>` | `true` | yes | `\u003cdiv>projected text\u003c/div>` |\n\nBoundaries, with hydration and `open` set to `false` on the server. `\u003capp-box>` is a component whose template is only `\u003cng-content />`.\n\n| Template inside `\u003capp-container [open]=\"open()\">` | `\u003capp-container>` after opening |\n| --- | --- |\n| `\u003cdiv>\u003cspan>\u003cng-content />\u003c/span>\u003c/div>` | `\u003cdiv>\u003cspan>\u003c/span>\u003c/div>` |\n| `\u003cdiv>\u003cng-container>\u003cng-content />\u003c/ng-container>\u003c/div>` | `\u003cdiv>\u003c/div>` |\n| `\u003cdiv>\u003cb>before\u003c/b>\u003cng-content />\u003c/div>` | `\u003cdiv>\u003cb>before\u003c/b>\u003c/div>` |\n| `\u003cdiv>\u003cng-content />\u003c/div>`, with `\u003cb>projected element\u003c/b>` projected into `\u003capp-wrapper>` | `\u003cdiv>\u003c/div>` |\n| `\u003cdiv>\u003cng-content select=\"b\" />\u003cng-content />\u003c/div>`, with `\u003cb>b\u003c/b> text` projected | `\u003cdiv>\u003c/div>` |\n| `\u003capp-box>\u003cdiv>\u003cng-content />\u003c/div>\u003c/app-box>` | `\u003capp-box>\u003cdiv>\u003c/div>\u003c/app-box>` |\n| `\u003cng-content />` | `projected text` (correct) |\n| `\u003cng-container>\u003cng-content />\u003c/ng-container>` | `projected text` (correct) |\n| `@if (true) { \u003cdiv>\u003cng-content />\u003c/div> }` | `\u003cdiv>projected text\u003c/div>` (correct) |\n| `\u003cdiv>\u003capp-box>\u003cng-content />\u003c/app-box>\u003c/div>` | `\u003cdiv>\u003capp-box>projected text\u003c/app-box>\u003c/div>` (correct) |\n\nIn every row, the page hydrates with no NG05xx error and reuses the server-rendered `\u003cbutton>`, `\u003capp-wrapper>` and `\u003capp-container>`.\n\n### Please provide a link to a minimal reproduction of the bug\n\nInline reproduction, no third-party libraries.\n\n```sh\nnpx @angular/cli@22.3.0 new repro --ssr --defaults --skip-git\ncd repro\nrm src/app/app.html src/app/app.css src/app/app.spec.ts\n# add the files below\nnpx ng build # the default app.routes.server.ts prerenders '**', so the build renders '/' on the server\nnode dist/repro/server/server.mjs\n# open http://localhost:4000/ and click \"toggle\"\n```\n\n`src/app/container.ts`\n\n```ts\nimport { Component, input } from '@angular/core';\n\n@Component({\n selector: 'app-container',\n template: `\n @if (open()) {\n \u003cng-content />\n }\n `,\n})\nexport class ContainerComponent {\n readonly open = input(false);\n}\n```\n\n`src/app/wrapper.ts`\n\n```ts\nimport { Component, input } from '@angular/core';\nimport { ContainerComponent } from './container';\n\n@Component({\n selector: 'app-wrapper',\n imports: [ContainerComponent],\n template: `\n \u003capp-container [open]=\"open()\">\n \u003cdiv>\u003cng-content />\u003c/div>\n \u003c/app-container>\n `,\n})\nexport class WrapperComponent {\n readonly open = input(false);\n}\n```\n\n`src/app/app.ts`\n\n```ts\nimport { Component, signal } from '@angular/core';\nimport { WrapperComponent } from './wrapper';\n\n@Component({\n selector: 'app-root',\n imports: [WrapperComponent],\n template: `\n \u003cbutton id=\"toggle\" (click)=\"open.set(!open())\">toggle\u003c/button>\n \u003capp-wrapper [open]=\"open()\">projected text\u003c/app-wrapper>\n `,\n})\nexport class App {\n protected readonly open = signal(false);\n}\n```\n\n`src/app/app.config.ts` (the generated providers, unchanged)\n\n```ts\nimport { ApplicationConfig, provideBrowserGlobalErrorListeners } from '@angular/core';\nimport { provideRouter } from '@angular/router';\nimport { provideClientHydration } from '@angular/platform-browser';\nimport { routes } from './app.routes';\n\nexport const appConfig: ApplicationConfig = {\n providers: [provideBrowserGlobalErrorListeners(), provideRouter(routes), provideClientHydration()],\n};\n```\n\n`src/app/app.config.server.ts` and `src/app/app.routes.server.ts` are the generated ones (`provideServerRendering(withRoutes(serverRoutes))`, `{ path: '**', renderMode: RenderMode.Prerender }`). To serve the build on `localhost`, `angular.json` has `\"allowedHosts\": [\"localhost\"]` under `security`.\n\n### Please provide the exception or error you saw\n\nThere is no exception. The prerendered `/` (production build) is:\n\n```html\n\u003capp-root ng-version=\"22.3.0\" ngh=\"2\" ng-server-context=\"ssg\">\u003cbutton id=\"toggle\" jsaction=\"click:;\">toggle\u003c/button>\u003capp-wrapper ngh=\"1\">\u003capp-container ngh=\"0\">\u003c!---->\u003c/app-container>\u003c/app-wrapper>\u003c/app-root>\n```\n\nwith this `__nghData__`:\n\n```json\n[{\"t\":{\"0\":\"t0\"},\"c\":{\"0\":[]}},{\"d\":[1]},{\"d\":[3]}]\n```\n\nAfter hydration and one click on \"toggle\", the content of `\u003capp-container>` is `\u003cdiv>\u003c/div>`. Without `provideClientHydration()`, it is `\u003cdiv>projected text\u003c/div>`.\n\nThe console of the development build only has:\n\n```\nAngular is running in development mode.\nAngular hydrated 3 component(s) and 9 node(s), 0 component(s) were skipped. 0 defer block(s) were configured to use incremental hydration. Learn more at https://v22.angular.dev/guide/hydration.\n```\n\nThe production build logs nothing.\n\n### Please provide the environment you discovered this bug in (run `ng version`)\n\n```\nAngular CLI : 22.3.0\nAngular : 22.3.0\nNode.js : 24.22.3\nPackage Manager : npm 11.19.1\nOperating System : linux x64\n\n┌───────────────────────────┬───────────────────┬───────────────────┐\n│ Package │ Installed Version │ Requested Version │\n├───────────────────────────┼───────────────────┼───────────────────┤\n│ @angular/build │ 22.3.0 │ ^22.3.0 │\n│ @angular/cli │ 22.3.0 │ ^22.3.0 │\n│ @angular/common │ 22.3.0 │ ^22.3.0 │\n│ @angular/compiler │ 22.3.0 │ ^22.3.0 │\n│ @angular/compiler-cli │ 22.3.0 │ ^22.3.0 │\n│ @angular/core │ 22.3.0 │ ^22.3.0 │\n│ @angular/forms │ 22.3.0 │ ^22.3.0 │\n│ @angular/platform-browser │ 22.3.0 │ ^22.3.0 │\n│ @angular/platform-server │ 22.3.0 │ ^22.3.0 │\n│ @angular/router │ 22.3.0 │ ^22.3.0 │\n│ @angular/ssr │ 22.3.0 │ ^22.3.0 │\n│ rxjs │ 7.8.2 │ ~7.8.0 │\n│ typescript │ 6.0.3 │ ~6.0.2 │\n│ vitest │ 5.1.1 │ ^5.0.0 │\n└───────────────────────────┴───────────────────┴───────────────────┘\n```\n\nThe same app also loses the content on 21.2.26 and on 20.3.35 (with `provideZoneChangeDetection({ eventCoalescing: true })` added on 20.x, as generated), in development and production builds.\n\n### Anything else?\n\n#### Cause\n\nOn the server, `\u003capp-container>` does not render its slot, so the `\u003cdiv>` and the projected text never reach the document. `serializeLView` records them as disconnected: in the `__nghData__` above, `\"d\":[1]` is the `\u003cdiv>` in `WrapperComponent` and `\"d\":[3]` is the text in `App`.\n\nOn the client:\n\n1. The text node in `App` is created, because it is disconnected. It is not inserted anywhere yet: its parent is the `\u003capp-wrapper>` host, and the content of a component is inserted by that component's `ɵɵprojection`.\n2. In `WrapperComponent`, `ɵɵelementStart` for the `\u003cdiv>` calls `canHydrateNode`, which returns `false` for a disconnected node, so a new `\u003cdiv>` is created.\n3. `ɵɵprojection` for the `\u003cng-content />` inside that `\u003cdiv>` skips `applyProjection`, because the view has hydration info.\n4. When `open` becomes `true`, the `@if` view of `ContainerComponent` is created without hydration info. Its `ɵɵprojection` moves the `\u003cdiv>` into `\u003capp-container>`, and the `\u003cdiv>` is still empty.\n\nStep 3 is in [`packages/core/src/render3/instructions/projection.ts#L194-L204`](https://github.com/angular/angular/blob/73916540c1688c0463617ef1469bf63adb0a628f/packages/core/src/render3/instructions/projection.ts#L194-L204) (`main` at `7391654`):\n\n```ts\n const hydrationInfo = lView[HYDRATION];\n const isNodeCreationMode = !hydrationInfo || isInSkipHydrationBlock();\n const componentHostNode = lView[DECLARATION_COMPONENT_VIEW][T_HOST] as TElementNode;\n const isEmpty = componentHostNode.projection![tProjectionNode.projection] === null;\n\n if (isEmpty && fallbackIndex !== null) {\n insertFallbackContent(lView, tView, fallbackIndex);\n } else if (isNodeCreationMode && !isDetachedByI18n(tProjectionNode)) {\n // re-distribution of projectable nodes is stored on a component's view level\n applyProjection(tView, lView, tProjectionNode);\n }\n```\n\nSkipping `applyProjection` while hydrating is right when the slot's parent was hydrated, because the projected nodes are already in it. Here the parent was created on the client, so the projected nodes were created on the client too, and nothing inserts them.\n\nThe rows of the boundaries table that work match this reading:\n\n- With `\u003cng-content />` directly in `\u003capp-container>`, or inside an `\u003cng-container>`, step 4 inserts the text, because `applyProjectionRecursive` walks into nested `\u003cng-content>` slots and into the children of `\u003cng-container>`. It does not walk into the children of an element.\n- With `\u003cdiv>\u003capp-box>\u003cng-content />\u003c/app-box>\u003c/div>`, the host of `\u003capp-box>` is created on the client, so its view has no hydration info and its own `ɵɵprojection` inserts the text.\n- With `@if (true) { \u003cdiv>\u003cng-content />\u003c/div> }`, the `@if` view is created without hydration info, so its `ɵɵprojection` runs in creation mode.\n\n#### Proposed fix\n\nTreat the slot as being in creation mode when its parent was not hydrated. `canHydrateNode` ([`packages/core/src/hydration/utils.ts#L523-L532`](https://github.com/angular/angular/blob/73916540c1688c0463617ef1469bf63adb0a628f/packages/core/src/hydration/utils.ts#L523-L532)) is the check that the element, `\u003cng-container>`, text and template instructions already use, through their `locateOrCreate…` functions, to decide whether to create a node. Applied to the slot's parent, it tells whether that parent was created on the client.\n\n```diff\n--- a/packages/core/src/render3/instructions/projection.ts\n+++ b/packages/core/src/render3/instructions/projection.ts\n@@ -5,6 +5,7 @@\n * Use of this source code is governed by an MIT-style license that can be\n * found in the LICENSE file at https://angular.dev/license\n */\n+import {canHydrateNode} from '../../hydration/utils';\n import {findMatchingDehydratedView} from '../../hydration/views';\n import {isDetachedByI18n} from '../../i18n/utils';\n import {newArray} from '../../util/array_utils';\n@@ -192,7 +193,15 @@\n setCurrentTNodeAsNotParent();\n \n const hydrationInfo = lView[HYDRATION];\n- const isNodeCreationMode = !hydrationInfo || isInSkipHydrationBlock();\n+ const parentTNode = tProjectionNode.parent;\n+ // While hydrating, the projected nodes are already in place in the DOM, so they are not\n+ // inserted again. The exception is a slot whose parent was created on the client: it was\n+ // disconnected from the DOM on the server (for example, inside content that was not\n+ // projected), so the projected nodes were created on the client as well and must be inserted.\n+ const isNodeCreationMode =\n+ !hydrationInfo ||\n+ isInSkipHydrationBlock() ||\n+ (parentTNode !== null && !canHydrateNode(lView, parentTNode));\n const componentHostNode = lView[DECLARATION_COMPONENT_VIEW][T_HOST] as TElementNode;\n const isEmpty = componentHostNode.projection![tProjectionNode.projection] === null;\n```\n\n`text.ts`, `element.ts`, `element_container.ts` and `template.ts` in the same folder already import `canHydrateNode` from `../../hydration/utils`.\n\nI applied the same condition to the compiled `@angular/core` 22.3.0 of the reproduction (`fesm2022/_debug_node-chunk.mjs`, in `ɵɵprojection`) and ran every row above, in development and production builds:\n\n- Every row that lost the content now shows it: `\u003cdiv>projected text\u003c/div>`, `\u003cdiv>\u003cspan>projected text\u003c/span>\u003c/div>`, `\u003cdiv>\u003cb>before\u003c/b>projected text\u003c/div>`, `\u003cdiv>\u003cb>projected element\u003c/b>\u003c/div>`, `\u003cdiv>\u003cb>b\u003c/b> text\u003c/div>`, `\u003capp-box>\u003cdiv>projected text\u003c/div>\u003c/app-box>`. It hides on the second click and shows again on the third.\n- The rows that already worked give the same content as without the change, including `open` set to `true` on the server, where the server-rendered `\u003cdiv>` is reused.\n- The server output does not change: the prerendered HTML and `__nghData__` are identical with and without the change. The change only affects the client, since `withDomHydration` does not enable the hydration runtime when `ngServerMode` is set, so `lView[HYDRATION]` is `null` on the server.\n- Hydration does not change: the server-rendered `\u003cbutton>`, `\u003capp-wrapper>` and `\u003capp-container>` are reused, the development build logs the same `Angular hydrated N component(s) and M node(s)` counts as without the change, and there is no NG05xx error or any other console output.\n\nIt also does not interact with #72129. With and without the one-line fix proposed there, in development and production builds, the rows of the #72129 table give the results below. The fix in #72131 narrows that condition to content-projected nodes; every node that follows a slot in these rows is projected into `\u003capp-container>`, so the condition matches the same nodes there.\n\n| Template inside `\u003capp-container [open]=\"open()\">` | `open` on the server | Unpatched | #72129 fix | This fix | Both |\n| --- | --- | --- | --- | --- | --- |\n| `\u003cng-content />@if (true) { \u003cp>after\u003c/p> }` | `false` | NG0502 | `projected text\u003cp>after\u003c/p>` | NG0502 | `projected text\u003cp>after\u003c/p>` |\n| `\u003cng-content />@if (true) { \u003cp>after\u003c/p> }` | `true` | `projected text\u003cp>after\u003c/p>` | same | same | same |\n| `\u003cng-content />` | `false` | `projected text` | same | same | same |\n| `\u003cng-content />\u003cp>after\u003c/p>` | `false` | NG0502 | `projected text\u003cp>after\u003c/p>` | NG0502 | `projected text\u003cp>after\u003c/p>` |\n| `\u003cng-content />after` | `false` | NG0502 | `projected textafter` | NG0502 | `projected textafter` |\n| `\u003cng-content />\u003cng-container>after\u003c/ng-container>` | `false` | NG0502 | `projected textafter` | NG0502 | `projected textafter` |\n| `\u003cng-content />@for (i of [1]; track i) { \u003cp>{{ i }}\u003c/p> }` | `false` | NG0502 | `projected text\u003cp>1\u003c/p>` | NG0502 | `projected text\u003cp>1\u003c/p>` |\n| `\u003cdiv>\u003cng-content />@if (true) { \u003cp>after\u003c/p> }\u003c/div>` | `false` | NG0502 | `\u003cdiv>\u003cp>after\u003c/p>\u003c/div>` | NG0502 | `\u003cdiv>projected text\u003cp>after\u003c/p>\u003c/div>` |\n| `\u003cp>before\u003c/p>\u003cng-content />` | `false` | `\u003cp>before\u003c/p>projected text` | same | same | same |\n| `\u003cng-content select=\"b\" />\u003cng-content />` | `false` | `projected text` | same | same | same |\n| `@let x = 1;@if (true) { \u003cp>{{ x }}\u003c/p> }` (no `\u003cng-content>`) | `false` | NG0502 | `\u003cp>1\u003c/p>` | NG0502 | `\u003cp>1\u003c/p>` |\n| `\u003cng-content />@let x = 1;` | `false` | `projected text` | same | same | same |\n\nThe `\u003cdiv>` row needs both fixes: the #72129 fix lets it render on the server, and this fix restores the projected text in the `\u003cdiv>`.\n\nA narrower alternative only checks the disconnected-node list: `parentTNode !== null && isDisconnectedNode(hydrationInfo, parentTNode.index - HEADER_OFFSET)`. It gave the same results on every row above. `canHydrateNode` also covers a parent detached by i18n, which I did not test.\n\nI have not run Angular's own test suite with the change.\n\n#### Suggested regression test\n\nIn `packages/platform-server/test/full_app_hydration_spec.ts`, in `describe('partial projection')`, next to \"should support cases when some element nodes are not projected (@if)\" (currently [line 5393](https://github.com/angular/angular/blob/73916540c1688c0463617ef1469bf63adb0a628f/packages/platform-server/test/full_app_hydration_spec.ts#L5393)). It uses only helpers and symbols the spec already imports (`Input`, `signal`). I have not run it in the Angular repository.\n\n```ts\nit('should project content into an element that was not projected on the server', async () => {\n @Component({\n selector: 'app-container',\n template: `\n @if (open) {\n \u003cng-content />\n }\n `,\n })\n class ContainerComponent {\n @Input() open = false;\n }\n\n @Component({\n selector: 'app-wrapper',\n imports: [ContainerComponent],\n template: `\n \u003capp-container [open]=\"open\">\n \u003cdiv>\u003cng-content />\u003c/div>\n \u003c/app-container>\n `,\n })\n class WrapperComponent {\n @Input() open = false;\n }\n\n @Component({\n selector: 'app',\n imports: [WrapperComponent],\n template: `\u003capp-wrapper [open]=\"open()\">projected text\u003c/app-wrapper>`,\n })\n class SimpleComponent {\n open = signal(false);\n }\n\n const html = await ssr(SimpleComponent);\n const ssrContents = getAppContents(html);\n\n expect(ssrContents).toContain('\u003capp ngh');\n expect(ssrContents).not.toContain('projected text');\n\n resetTViewsFor(SimpleComponent, WrapperComponent, ContainerComponent);\n\n const appRef = await prepareEnvironmentAndHydrate(doc, html, SimpleComponent);\n const compRef = getComponentRef\u003cSimpleComponent>(appRef);\n appRef.tick();\n\n const clientRootNode = compRef.location.nativeElement;\n verifyAllNodesClaimedForHydration(clientRootNode);\n verifyClientAndSSRContentsMatch(ssrContents, clientRootNode);\n\n // The content that was not projected on the server renders once the slot opens.\n compRef.instance.open.set(true);\n appRef.tick();\n\n expect(clientRootNode.querySelector('app-container > div').textContent).toBe('projected text');\n});\n```\n\nWithout the fix, I expect the last expectation to fail with an empty `\u003cdiv>`, as in the reproduction.\n\n#### Related\n\n- #72129: same family (nodes in content that is not projected), but a different mechanism. That bug fails on the server, in `serializeLView`, when a node follows `\u003cng-content>`. This one happens on the client, in `ɵɵprojection`, and needs no sibling. The two fixes are independent. #72131 is the pull request for #72129.\n- Possibly related: #50175 reported the same symptom in 2023 (\"the ng-content is filled with nothing\", with Angular Material). According to the analysis in that issue, its cause was a view container projected into a component that skips hydration, and it was fixed in 16.0.1.\n","author":{"url":"https://github.com/floxcristian","@type":"Person","name":"floxcristian"},"datePublished":"2026-11-19T19:18:15Z","url":"https://github.com/angular/angular/issues/72132"}
| 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:7c9009dd-b667-b33a-3225-28adde689361 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | D1BE:17FB7:28D276B:33D7B09:6B01D629 |
| html-safe-nonce | b6d3108ceb9ff1bb212b78bb9875377feccbcf22b12923075f34821ab154852f |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJEMUJFOjE3RkI3OjI4RDI3NkI6MzNEN0IwOTo2QjAxRDYyOSIsInZpc2l0b3JfaWQiOiI1MzY2MzMzODYzMTQ2NjczNzA1IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 59ccf56d04368eebeddeb85edd7bf24138b0481e344a71266c8f1e872f04d210 |
| hovercard-subject-tag | issue:6497205448 |
| 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/72132/issue_layout |
| twitter:image | https://opengraph.githubassets.com/6beedf3a65bdd1964a07bb0576afa848de314219ff93ccfa5f23ec9d054cf18f/angular/angular/issues/72132 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/6beedf3a65bdd1964a07bb0576afa848de314219ff93ccfa5f23ec9d054cf18f/angular/angular/issues/72132 |
| og:image:alt | Which @angular/* package(s) are the source of the bug? core Is this a regression? No It reproduces on 20.3.35, 21.2.26 and 22.3.0 (the current latest), in development and production builds. Descrip... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | floxcristian |
| 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